diff options
| author | blasty <blasty@local> | 2026-07-24 15:33:17 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-24 15:33:17 +0200 |
| commit | 731bca5c31f3507424a391fecf081be1a6c6717d (patch) | |
| tree | b089dab655490cefe3f59554c0a4845a94e49035 /docs/RPC.md | |
| parent | listing: shift+home jumps to the start of the instruction text (diff) | |
| download | ida-tui-731bca5c31f3507424a391fecf081be1a6c6717d.tar.gz ida-tui-731bca5c31f3507424a391fecf081be1a6c6717d.tar.xz ida-tui-731bca5c31f3507424a391fecf081be1a6c6717d.zip | |
xrefs: show fine-grained kind (call/jump/read/write/offset) in the dialog
ida-pro-mcp's xref_query only classifies xrefs as code/data (xr.iscode). Add an
injected `xref_types` tool (server/patch_server.py) that mirrors xref_query's
query/envelope shape but derives a fine `kind` from the IDA xref type:
call/jump/flow for code (fl_CF/CN/JF/JN/F), read/write/offset/text/info for data
(dr_R/W/O/T/I). The worker self-injects it on startup like the other custom tools.
* domain: Xref gains a `kind` field; _parse_xrefs reads it; xrefs_to() now calls
xref_types (falling back to xref_query if absent). xrefs_from is unchanged.
* app: the `x` dialog shows the kind as an aligned column after the address
(`000034F4 read sub_34F0+0x4`).
* rpc: the structured xrefs_to read carries `kind` too.
Verified live over the worker/RPC harness on targets/echo: sub_2C00 callers ->
call; __progname -> offset (GOT), read (sub_34F0), write (sub_3500); stdout ->
read/offset.
Diffstat (limited to 'docs/RPC.md')
0 files changed, 0 insertions, 0 deletions