On startup, GUD runs one of the following hooks:
if you are using GDB;
dbx-mode-hook, if you are using DBX;
sdb-mode-hook, if you are using SDB;
xdb-mode-hook, if you
are using XDB;
perldb-mode-hook, for Perl debugging mode;
jdb-mode-hook, for PDB;
jdb-mode-hook, for JDB. You can
use these hooks to define custom key bindings for the debugger
interaction buffer. See section Hooks.
Here is a convenient way to define a command that sends a particular command string to the debugger, and set up a key binding for it in the debugger interaction buffer:
(gud-def function cmdstring binding docstring)
This defines a command named function which sends
cmdstring to the debugger process, and gives it the documentation
string docstring. You can use the command thus defined in any
buffer. If binding is non-
gud-def also binds
the command to C-c binding in the GUD buffer's mode and to
C-x C-a binding generally.
The command string cmdstring may contain certain `%'-sequences that stand for data to be filled in at the time function is called:
Go to the first, previous, next, last section, table of contents.