Instructions

149 C-Control Pro IDE

3.4 Debugger

In order to activate the Debugger the project must first be compiled in Debug Code free of errors and

then transferred to the Module. The file holding the Debug Code (*.dbg) must be present in the pro-

ject list.

In the Debugger menu all Debugger commands can be found. The Debugger ist started with Debug

Mode (Shift-F10). If at this point of time no Breakpoint is set then the Debugger will stop at the first

executable instruction.

If in Debug Mode, the next Breakpoint will be reached by use of Start (F10). If no Breakpoint is set

then the program will be executed in its normal way. There is the exception however that the pro-

gram flow can be stopped by use of Stop Program. This only works providing that the program has

been started from the Debug Mode.

If the Debugger has stopped in the program (a blue bar is displayed) then the program can be ex-

ecuted in single steps. The instructions Single Step (Shift-F8) and Procedure Step (F8) respectively

will execute the program code up to the next code line and will then stop again. Opposing to Single

Step the function Procedure Step will not jump into the function calls but will overpass them. If the

program has stopped all breakpoints can be changed.

If a loop contains only one code line then one single step will execute the entire loop since only

after this branching out to a new code line will take place.

With the instruction Leave Debug Mode the Debug Mode will be terminated.

During active Debug Mode the program text can not be altered. This is because line numbers

holding set Breakpoints must not be moved out of place. Otherwise the Debugger would not be able

to synchronize with the Bytecode onto the C-Control Module.