Trace-based Debugging (CTS)
Standard Trace-based Debugging requires:
Forward and backward debugging of traced program section
Any record in the trace can be selected as starting point for Trace-based Debugging.
As soon as the starting point is selected TRACE32 reconstructs in its GUI the context of the target system as it was when the instruction at the
starting point was executed.
When the reconstruction is finished the program steps previously recorded in real-time in the trace memory can be debugged again in TRACE32 PowerView.
The following debugging commands are available for forward debugging:
The following debugging commands are available for backward debugging:
Trace display including all local variable
The fact that TRACE32 can reconstruct the register and memory contents for any trace sampling points allows the user to display a full high-level language trace including all register and stack variables.
Function nesting display
Function run-time timing display
Filling the trace gaps
If more trace information is generated than the trace interface can output, trace information can be lost. The result are trace gaps
(TARGET FIFO OVERFLOWs).
The Trace-based Debugging technology enables TRACE32 to fill in most of these gaps. These records are marked as "s"ynthetically reconstructed (exes instead of exec in the example above).
Copyright © 2019 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 06-May-2019