Previous: Frame Evaluation, Up: Interactive Debugger


3.4.4.5 Single Stepping and Continuing Execution

The commands in this subsection all apply only when the stack is continuable — in other words when it makes sense for the program that the stack comes from to continue running. Usually this means that the program stopped because of a trap or a breakpoint.

— Debugger Command: step [n]

Tell the debugged program to do n more steps from its current position. One step means executing until the next frame entry or exit of any kind. n defaults to 1.

— Debugger Command: next [n]

Tell the debugged program to do n more steps from its current position, but only counting frame entries and exits where the corresponding source code comes from the same file as the current stack frame. (See Step Traps for the details of how this works.) If the current stack frame has no source code, the effect of this command is the same as of step. n defaults to 1.

— Debugger Command: finish

Tell the program being debugged to continue running until the completion of the current stack frame, and at that time to print the result and reenter the command line debugger.

— Debugger Command: continue

Tell the program being debugged to continue running. (In fact this is the same as the quit command, because it exits the debugger command loop and so allows whatever code it was that invoked the debugger to continue.)