If it makes sense to continue execution from the stack which is being displayed, GDS provides the following further commands in the stack buffer.
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
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.
gds-step-into). i therefore steps through code at the most detailed level possible.
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.