3.5.6 Continuing Execution

If it makes sense to continue execution from the stack which is being displayed, GDS provides the following further commands in the stack buffer.

g, c, q

Tell the program to continue running (gds-go). It may of course stop again if it hits another trap, or another occurrence of the same trap.

The multiple keystrokes reflect that you can think of this as “going”, “continuing” or “quitting” (in the sense of quitting the GDS display).

<SPC>

Tell the program to do a single-step to the next entry or exit of a frame whose code comes from the same source file as the selected stack frame (gds-step-file).

In other words, you can hit <SPC> repeatedly to step through the code in a given file, automatically stepping over any evaluations or procedure calls that use code from other files (or from no file).

If the selected stack frame has no source, the effect of this command is the same as that of i, described next.

i

Tell the debugged program to do a single-step to the next frame entry or exit of any kind (gds-step-into). i therefore steps through code at the most detailed level possible.

o

Tell the debugged program to continue running until the selected stack frame completes, and then to display its result (gds-step-over). Note that the program may stop before then if it hits another trap; in this case the trap telling it to stop when the marked frame completes remains in place and so will still fire at the appropriate point.