Debugger Operation Debuggers GUD Customization
The GUD interaction buffer uses a variant of Shell mode, so the commands of Shell mode are available (see Shell Mode). GUD mode also provides commands for setting and clearing breakpoints, for selecting stack frames, and for stepping through the program. These commands are available both in the GUD buffer and globally, but with different key bindings.
The breakpoint commands are usually used in source file buffers, because that is the way to specify where to set or clear the breakpoint. Here's the global command to set a breakpoint:
Set a breakpoint on the source line that point is on.
Here are the other special commands provided by GUD. The keys starting with C-c are available only in the GUD interaction buffer. The key bindings that start with C-x C-a are available in the GUD interaction buffer and also in source files.
Display in another window the last line referred to in the GUD
buffer (that is, the line indicated in the last location message).
This runs the command
Execute a single line of code (
Execute a single line of code, stepping across entire function calls
at full speed (
Execute a single machine instruction (
Continue execution without specifying any stopping point. The program
will run until it hits a breakpoint, terminates, or gets a signal that
the debugger is checking for (
Delete the breakpoint(s) on the current source line, if any
Set a temporary breakpoint on the current source line, if any. If you use this command in the GUD interaction buffer, it applies to the line where the program last stopped.
The above commands are common to all supported debuggers. If you are using GDB or (some versions of) DBX, these additional commands are available:
Select the next enclosing stack frame (
Select the next inner stack frame (
If you are using GDB, these additional key bindings are available:
With GDB, complete a symbol name (
Run the program until the selected stack frame returns (or until it stops for some other reason).
These commands interpret a numeric argument as a repeat count, when that makes sense.
TAB serves as a completion command, you can't use it to
enter a tab as input to the program you are debugging with GDB.
Instead, type C-q
TAB to enter a tab.