Controlling debug execution
The debug execution controls are superceded by breakpoints. For example, if you attempt to step over a function and the program hits a breakpoint, it pauses, regardless of whether the function is completed. You can control your debug execution in various ways, but they all rely on a core set of debug controls.
To control a debug execution:
- In the Debug view, select a thread
- To control the debug session, click menu items
- Debug > Reset
- Debug > Run
- Debug > Suspend
- Debug > Terminate
- Debug > Step Into
- Debug > Step Over
- Debug > Step Out
- Debug > Run to line
- Or directly click the toolbar buttons
- Or use the keyboard shortcuts
| Icons |
Action |
Description |
Keyboard shortcut |
 |
Reset |
Select the Reset command to reset the debugging. |
|
 |
Run |
Select the Run command to resume execution of the currently suspended debug target. |
F5 |
 |
Suspend |
Select the Suspend command to halt execution of the currently selected thread in a debug target. |
F9 |
 |
Terminate |
Ends the selected debug session and/or process. The impact of this action depends on the type of the item selected in the Debug view. |
Ctrl + F5 |
 |
Step Into |
Select to execute the current line, including any routines, and proceed to the next statement. |
F11 |
 |
Step Over |
Select to execute the current line, following execution inside a routine. |
F12 |
 |
Step Out |
Select to continue execution to the end of the current routine, then follow execution to the routine's caller. |
F7 |
 |
Run to Line |
Select to continue execution to current line. |
Ctrl + R |
|
CoIDE User Guide (for 1.5.1)
|