aboutsummaryrefslogtreecommitdiffstats
path: root/experiments
diff options
context:
space:
mode:
authorblasty <blasty@local>2026-07-24 23:38:30 +0200
committerblasty <blasty@local>2026-07-24 23:38:30 +0200
commitde2fa194278bb132e23edddd65bdad84f32ec37d (patch)
tree67d18789676b3377892d3edf4a6fbe4d497967af /experiments
parentsplit-view phase 2: cursor sync + linked-row highlight (diff)
downloadida-tui-de2fa194278bb132e23edddd65bdad84f32ec37d.tar.gz
ida-tui-de2fa194278bb132e23edddd65bdad84f32ec37d.tar.xz
ida-tui-de2fa194278bb132e23edddd65bdad84f32ec37d.zip
split-view phase 3: rich per-line instruction region highlight
The Ghidra "region band": moving the pseudocode cursor now lights up EVERY instruction that C line owns, not just one. * server/patch_server.py: new decomp_map tool — sweeps cfunc.get_line_item across each pseudocode line's columns and collects the ea from each item's dstr() ('EA: desc', matching the /*ea*/ marker source so it aligns with the display lines). Returns {addr, lines:[{ea, eas:[...]}]}. (First tried item.get_ea(), which reports a different ea and didn't align — dstr() is the right source.) * domain: Program.decomp_map(ea) -> per-line ea lists, cached by name-gen. * app: _load_split_map fetches it off-thread into _split_eamap/_split_ea2line; _sync_split bands the full instruction region for a C line (decomp drives) and uses the exact ea->line inverse (listing drives), falling back to the single marker until the map lands. Maps cleared on leaving split. Pilot split_view gains: decomp_map returns/aligns with the markers, and a multi-instruction C line bands >1 listing row (13/13). Full suite 154/2-flake. The idalib spike ran on the pilot's own worker (the standalone worker kept getting reaped in this sandbox).
Diffstat (limited to 'experiments')
0 files changed, 0 insertions, 0 deletions