Collect Execution History of Programs

2.11 Collect Execution History of Programs

This section describes how to collect the execution history of the program.

A history of program execution is generally called a trace; this term will be used in the remainder of this document.

It is nearly impossible to find the cause of runaway program execution from the memory contents, stack information, and the like after the runaway has occurred. The collected trace data, however, can be used to trace program execution up to the runaway directly, making this an effective tool for discovering hidden bugs.

Caution 1.

[E1][E20][EZ Emulator]
The trace function is supported only when the selected microcontroller incorporates the OCD trace function.

Caution 2.

[Simulator]
4 bytes of the final address of the code flash area (when a code flash area is 0x0 - 0x1FFFF, 0x1FFFC - 1FFFFF corresponds to it) and the RAM area which can be fetched cannot be fetched (a message of "Stopped by accessing to no map area." will appear).