Instruction level tracing and replaying

Use single-step to trace the program execution and be able to replay the trace, same as how x64dbg/hopper does it. This is not as powerful as TTD, but it is a reasonable ask

Discussed in https://github.com/Vector35/debugger/discussions/1027

^{Originally posted by ivansavra1 March 24, 2026}
It would be very useful to have a tracing button in Binary Ninja, similarly to what Hopper Disassembler offers when debugging. Currently, you have to step through the instructions and note the route, which is impractical, ideally it should be automatic, and save the route by coloring each block.
You could even expand this by enabling tracing of the whole binary instead of just one function, I know there's TTD but that's only for Windows and Linux, Mac users have no TTD and thus zero built-in tracing.

Start by reading discussion 1027 and examining the debugger's existing single-step and TTD-related behavior. Define the supported tracing scope, replay model, and user-visible completion criteria before identifying implementation entry points; done means a trace can be captured and replayed as described without relying on platform-specific TTD.