Using SoftBench Debugger

Stepping through Your Program

Stepping through Your Program

When SoftBench Debugger loads a program, it begins executing the program and pauses at the first line with a breakpoint. You can then use SoftBench Debugger to execute your program one or more statements at a time.

In the default configuration, SoftBench Debugger displays the following buttons above the Debugger Output Area:

Step

Execute one statement, then stop. This is called single

 

step execution.

Step Over

Execute a statement, treating any procedure call as a

 

single statement. SoftBench Debugger calls the

 

procedure, but control does not return to the debugger

 

until the procedure returns. When the PC is just before

 

a procedure call, this has the effect of "stepping over"

 

the call.

Continue Out

Finish executing the current procedure. Run without

 

stopping until the current procedure completes and

 

returns to its caller (or until SoftBench Debugger

 

encounters another breakpoint or similar event), then

 

stop. Use this when you accidentally step into a

 

procedure that you do not want to step through, or

 

when you interrupt your program in the middle of

 

non-debuggable code. Each Continue Out causes your

 

program to "pop out" one procedure level.

When you select one of these buttons, the PC arrow moves to the next statement to be executed.

SoftBench Debugger steps over undebuggable routines, such as system library routines and routines that were not compiled with the debug option, even when using Step.

To pause at a specific point in your program, see “Setting and Using Breakpoints” on page 189.

Chapter 7

171