diff options
| author | blasty <blasty@local> | 2026-07-27 22:03:08 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-27 22:03:08 +0200 |
| commit | a8d39781a7b03504556b5df6ff73ab2fd145efaf (patch) | |
| tree | e41254c0829d3a9f8eb25fe845845cba6f2d1157 /tests | |
| parent | trace: paint the execution trail — including on the decompiler (diff) | |
| download | ida-tui-a8d39781a7b03504556b5df6ff73ab2fd145efaf.tar.gz ida-tui-a8d39781a7b03504556b5df6ff73ab2fd145efaf.tar.xz ida-tui-a8d39781a7b03504556b5df6ff73ab2fd145efaf.zip | |
rpc: a `trace` verb, and --trace for pane spawn
Driving the trace viewer needed the same treatment as everything else: seeking by
hand through a few hundred keypresses to reach an interesting timestamp is not a
way to test it.
trace {seek: 120} absolute timestamp
trace {seek: "!50"} halfway through, like Tenet's timestamp shell
trace {goto: "main"} first execution of a name or 0xADDR
trace {step: 20} relative, negative goes back
trace {step: 5, over: true}
Returns the usual state snapshot plus {idx, length, pc, changed} so a driver can
see where it landed and what that instruction wrote.
pane spawn --trace FILE passes it through to the launcher, so a trace pane is one
command.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions