Introduction to using trace
See also:
Reasons for using trace
By using trace, you can inspect the program flow up to a specific state, for instance an application crash, and use the trace data to locate the origin of the problem. Trace data can be useful for locating programming errors that have irregular symptoms and occur sporadically.
Briefly about trace
To use trace in C-SPY requires that your target system can generate trace data. Once generated, C-SPY can collect it and you can visualize and analyze the data in various windows and dialog boxes.
Trace data is a continuously collected sequence of every executed instruction for a selected portion of the execution.
Trace features in C-SPY
In C-SPY, you can use the trace-related windows—Trace, Function Trace, Timeline, and Find in Trace.
Depending on your C-SPY driver, you:
Can set various types of trace breakpoints and triggers to control the collection of trace data.
Have access to windows such as the Interrupt Log, Interrupt Log Summary, Data Log, and Data Log Summary.
In addition, several other features in C-SPY also use trace data, features such as Profiling, Code coverage, and Instruction profiling.
Note
Because interrupt logging uses the trace data, trace and interrupt logging cannot be used simultaneously. If you use interrupt logging, you should disable trace, and vice versa.