You can always ask gdb itself for information on its commands,
using the command
h) with no arguments to display a short list of named classes of commands:
(gdb) help List of classes of commands: aliases -- Aliases of other commands breakpoints -- Making program stop at certain points data -- Examining data files -- Specifying and examining files internals -- Maintenance commands obscure -- Obscure features running -- Running the program stack -- Examining the stack status -- Status inquiries support -- Support facilities tracepoints -- Tracing of program execution without stopping the program user-defined -- User-defined commands Type "help" followed by a class name for a list of commands in that class. Type "help" followed by command name for full documentation. Command name abbreviations are allowed if unambiguous. (gdb)
(gdb) help status Status inquiries. List of commands: info -- Generic command for showing things about the program being debugged show -- Generic command for showing things about the debugger Type "help" followed by command name for full documentation. Command name abbreviations are allowed if unambiguous. (gdb)
helpargument, gdb displays a short paragraph on how to use that command.
aproposcommand searches through all of the gdb commands, and their documentation, for the regular expression specified in args. It prints out all matches found. For example:
alias -- Define a new command that is an alias of an existing command aliases -- Aliases of other commands d -- Delete some breakpoints or auto-display expressions del -- Delete some breakpoints or auto-display expressions delete -- Delete some breakpoints or auto-display expressions
completeargs command lists all the possible completions for the beginning of a command. Use args to specify the beginning of the command you want completed. For example:
if ignore info inspect
This is intended for use by gnu Emacs.
In addition to
help, you can use the gdb commands
show to inquire about the state of your program, or the state
of gdb itself. Each command supports many topics of inquiry; this
manual introduces each of them in the appropriate context. The listings
info and under
show in the Command, Variable, and
Function Index point to all the sub-commands. See Command and Variable Index.
i) is for describing the state of your program. For example, you can show the arguments passed to a function with
info args, list the registers currently in use with
info registers, or list the breakpoints you have set with
info breakpoints. You can get a complete list of the
set. For example, you can set the gdb prompt to a $-sign with
set prompt $.
showis for describing the state of gdb itself. You can change most of the things you can
show, by using the related command
set; for example, you can control what number system is used for displays with
set radix, or simply inquire which is currently in use with
To display all the settable parameters and their current
values, you can use
show with no arguments; you may also use
info set. Both commands produce the same display.
Here are three miscellaneous
show subcommands, all of which are
exceptional in lacking corresponding