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:

1. In the Debug view, select a thread
2. To control the debug session, click menu items
3. Debug > Run
4. Debug > Suspend
5. Debug > Terminate
6. Debug > Step Into
7. Debug > Step Over
8. Debug > Step Out



9. Or directly click the toolbar buttons
10. Or use the keyboard shortcuts
    
    

Icons	Action	Description	Keyboard shortcut
	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.	F6
	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

To change the key binding:

If you don't like the keyboard shortcuts settings, you can change the key binding. The function of the keyboard can be extensively customized in CoDebugger. Use the General > Keys preference page to assign key sequences to debug control commands.For example you want to change the Terminate key bindding to Ctrl + F2.

1. Click Window > Preferences. 2. Click General > Keys. 3. Find out the Terminate Command. 4. Delete the old key binding text Ctrl + F5 in binding text box. 5. Focus in the Binding text box and pressing CTRL and F2. 6. Click Apply.