Commands of GUD
Debuggers
On startup, GUD runs one of the following hooks: gdb-mode-hook,
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 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-nil, 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:
`%f'
|
The name of the current source file. If the current buffer is the GUD buffer, then the ``current source file'' is the file that the program stopped in. |
`%l'
|
The number of the current source line. If the current buffer is the GUD buffer, then the ``current source line'' is the line that the program stopped in. |
`%e'
|
The text of the C lvalue or function-call expression at or adjacent to point. |
`%a'
|
The text of the hexadecimal address at or adjacent to point. |
`%p'
|
The numeric argument of the called function, as a decimal number. If
the command is used without a numeric argument, `
If you don't use ` |
Commands of GUD
Debuggers