Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) Standard preamble: ========================================================================
NAMEgdb - The GNU Debugger
SYNOPSISgdb [-help] [-nh] [-nx] [-q] [-batch] [-cd=dir] [-f] [-b bps]
[-tty=dev] [-s symfile] [-e prog] [-se prog] [-c core] [-p procID]
[-x cmds] [-d dir] [prog|prog procID|prog core]
DESCRIPTIONThe purpose of a debugger such as
- Start your program, specifying anything that might affect its behavior.
- Make your program stop on specified conditions.
- Examine what has happened, when your program has stopped.
- Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.
You can use
You can run "gdb" with no arguments or options; but the most usual way to start
You can also start with both an executable program and a core file specified:
gdb program core
You can, instead, specify a process
gdb program 1234 gdb -p 1234
Here are some of the most frequently needed
- break [file:]function
- Set a breakpoint at function (in file).
- run [arglist]
- Start your program (with arglist, if specified).
- Backtrace: display the program stack.
- print expr
- Display the value of an expression.
- Continue running your program (after stopping, e.g. at a breakpoint).
- Execute next program line (after stopping); step over any function calls in the line.
- edit [file:]function
- look at the program line where it is presently stopped.
- list [file:]function
- type the text of the program in the vicinity of where it is presently stopped.
- Execute next program line (after stopping); step into any function calls in the line.
- help [name]
Show information about GDBcommand name, or general information about usingGDB.
Exit from GDB.
For full details on
OPTIONSAny arguments other than options specify an executable file and core file (or process
All the options and command line arguments you give are processed in sequential order. The order makes a difference when the -x option is used.
- List all options, with brief explanations.
- -s file
- Read symbol table from file file.
- Enable writing into executable and core files.
- -e file
- Use file file as the executable file to execute when appropriate, and for examining pure data in conjunction with a core dump.
- Read symbol table from file file and use it as the executable file.
- -c file
- Use file file as a core dump to examine.
- -x file
Execute GDBcommands from file file.
- -ex command
Execute given GDBcommand.
- -d directory
- Add directory to the path to search for source files.
- Do not execute commands from ~/.gdbinit.
- Do not execute commands from any .gdbinit initialization files.
- ``Quiet''. Do not print the introductory and copyright messages. These messages are also suppressed in batch mode.
Run in batch mode. Exit with status 0 after processing all the command
files specified with -x (and .gdbinit, if not inhibited).
Exit with nonzero status if an error occurs in executing the GDBcommands in the command files.
Batch mode may be useful for runningGDBas a filter, for example to download and run a program on another computer; in order to make this more useful, the message
Program exited normally.
(which is ordinarily issued whenever a program running underGDBcontrol terminates) is not issued when running in batch mode.
Run GDBusing directory as its working directory, instead of the current directory.
Emacs sets this option when it runs GDBas a subprocess. It tellsGDBto output the full file name and line number in a standard, recognizable fashion each time a stack frame is displayed (which includes each time the program stops). This recognizable format looks like two \032 characters, followed by the file name, line number and character position separated by colons, and a newline. The Emacs-to-GDB interface program uses the two \032 characters as a signal to display the source code for the frame.
- -b bps
Set the line speed (baud rate or bits per second) of any serial
interface used by GDBfor remote debugging.
- Run using device for your program's standard input and output.
SEE ALSOThe full documentation for
should give you access to the complete manual.
COPYRIGHTCopyright (c) 1988-2017 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the