When either of the following operation has occurred, the program will stop automatically after conducting step execution in the source level (1 line of source text) or in the instruction level (1 instruction).
Once the program is stopped, the contents of each panel will be updated automatically. As such, step execution is suited for debugging the program execution in transition either in source or instruction level.
The unit in which the program is step-executed is determined by the setting of the Editor panel as follows:
Step execution is conducted in source level.
Note, however, that when the focus is in the Disassemble panel or the line information does not exist in the address specified by the current PC value, the step execution is conducted in instruction level.
Step execution is conducted in instruction level.
Step execution is divided into the following types:
2.9.3.1 Step into the function (Step In execution)
2.9.3.2 Step over the function (Step Over execution)
2.9.3.3 Execute until return is completed (Return Out execution)
Break points, break events, and Printf events that have been set do not occur during step execution. |
During source-level stepping, the debugger may appear to be executing instructions that are not supposed to be executed. |
In the program code shown below, it seems that the position indicated by the current PC might be moved to position (*1) after the execution of (*2), although (*1) is never actually executed in the generated code. |
Note that this caution may be eliminated by setting the [Optimization level] property to [0 (-optimize=0)] in the [Optimization] category on the [Compile Options] tab in the Property panel of the build tool.