Trace view is a view in which you can see history of stepped instructions. This lets you examine the details of each instruction stepped when you are stepping manually or tracing automatically, or view a trace history previously saved. This functionality must be enabled explicitly from trace view or CPU view. It features saving all the instructions, registers and memory accesses during a trace.
You can double-click on columns to perform quick operation:
- Index: follow in disassembly.
- Address: toggle RVA display mode.
- Opcode: toggle breakpoint.
- Disassembly: follow in disassembly.
- Comments: set comments.
Start Run Trace¶
To enable trace logging into trace view, you first enable it via “Start Run Trace” menu. It will pop up a dialog allowing you to save the recorded instructions into a file. The default location of this file is in the database directory.
Once started, every instruction you stepped or traced will appear immediately in Trace view. Instructions executed while the debuggee is running or stepping over will not appear here.
Stop Run Trace¶
This menu can stop recording instructions.
Close current trace file and clear the trace view.
Close and delete¶
Close current trace file and clear the trace view, and also delete current trace file from disk.
Open a trace file to view the content of it. It can be used when not debugging, but it is recommended that you debug the corresponding debuggee when viewing a trace, as it will be able to render the instructions with labels from the database of the debuggee. The debugger will show a warning if you want to load a trace file which is not recorded from currently debugged executable.
Open a recent file to view the content of it.
Search for the user-specified constant in the entire recorded trace, and record the occurances in references view.
Search for memory accesses to the user-specified address.