Actions

At the top of the toolbar, there are multiple buttons which are responsible for debugger actions. These buttons are only active when a debug configuration is started.

Fig. 1. Stepping buttons

Resume button

Resume will start every core’s execution simultaneously and let them run until a breakpoint is hit, or the user stop the cores with the Suspend button. This button is only active when the cores are in a suspended state.

Fig. 2. Resume button’s icon

If the debugger hit a breakpoint, or the user previously pressed the Suspend button, the cores are in the suspended state, the Resume button can be used to start the cores.

Fig. 3. Resume is only active when the cores are suspended

After pressing Resume, the cores will start and run until one of the core hits a breakpoint, or the user presses the Suspend button.

Fig. 4. After pressing Resume, the cores will start

Suspend button

Suspend will stop every cores execution.

Fig. 5. Suspend button’s icon

This button can only be used when the cores are in the running state.

Fig. 6. Suspend is only active when the cores are running

After pressing Suspend, the cores will stop at the instruction where the execution was interrupted by pressing the Suspend button.

Fig. 7. After pressing Suspend, the cores will stop

Terminate button

The Terminate button is used to terminate the current debug launch. After termination, the debug configurations must be launched again to start the debugging again.

Fig. 8. Terminate button’s icon

The Terminate button is always active as long as the debug configuration is running. When pressing the Terminate button, de debugger will disconnect from the board and the debug session is over.

Fig. 9. The debugger will disconnect after pressing the Terminate button

Reset button

The Reset button is used to start the debug session from the beginning, it will reset every core’s execution. After reset, the debugger will go back to the Stop at function, if this is not defined in the debug configuration, then it will stop at the first user breakpoint.

Fig. 10. Reset button’s icon

The Reset button is always active during the debug session. When pressed, the debugger will restart the debug session.

Fig. 11. Before pressing Reset

Fig. 12. After pressing Reset, the debugger stops at the stop at function

Step Into button

The Step Into button can be used to step inside function calls. It will do regular stepping if the current source line is not a function call. It only performs the step on the currently selected core only.

Fig. 13. Step Into button’s icon

For function calls, the Step Into button will step inside the function, and the debug view will automatically jump to the functions definition.

Fig. 14. Before pressing Step Into

Fig. 15. After pressing Step Into, the debugger will jump to the function’s definition, and the user can continue the debug session from there

Step Over button

The Step Over button can be used to step over a source line in the source file (so it will jump over function calls). The step over works on the currently selected core only, so it is not synchronized across every core, just the selected core will do the stepping. The Step Over button can also be used to step over inline function calls.

Fig. 16. Step Over button’s icon

Step Over can be used to step over function calls in the code.

Fig. 17. Before pressing Step Over

Fig. 18. After pressing Step Over, the debugger will jump over the function call

Step Return button

The Step Return button can be used to step out from the current function.

Fig. 19. Step Return button’s icon

After pressing Step Return the debugger will step out from the currently executed function, and stop at the instruction after the function’s return.

Fig. 20. Before pressing Step Return

Fig. 21. After pressing Step Return, the debugger will jump out from the function

Instruction Stepping Mode button

The debugger is also able to switch between stepping modes. Not only source level stepping is supported, but assembly level stepping as well. This stepping mode can be switched with the Instruction Stepping Mode button.

Fig. 22. Instruction Stepping Mode button’s icon

After pressing the Instruction Stepping Mode button, the debugger will show the Disassembly view

Fig. 23. After pressing the Instruction Stepping Mode button

For assembly level stepping, it is useful to open the Disassembly view to see the currently executed binary instruction. To open the Disassembly view go to Window → Show View → Disassembly

Fig. 24. Opening the Disassembly View