Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35)

Standard preamble:
========================================================================
..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} .\}
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "GDB 1" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
gdb - The GNU Debugger Header "SYNOPSIS" gdb [-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] Header "DESCRIPTION" The purpose of a debugger such as \s-1GDB\s0 is to allow you to see what is going on \*(L"inside\*(R" another program while it executes \*(-- or what another program was doing at the moment it crashed.

\s-1GDB\s0 can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act:

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 \s-1GDB\s0 to debug programs written in C, C@t{++}, Fortran and Modula-2.

\s-1GDB\s0 is invoked with the shell command \*(C`gdb\*(C'. Once started, it reads commands from the terminal until you tell it to exit with the \s-1GDB\s0 command \*(C`quit\*(C'. You can get online help from \s-1GDB\s0 itself by using the command \*(C`help\*(C'.

You can run \*(C`gdb\*(C' with no arguments or options; but the most usual way to start \s-1GDB\s0 is with one argument or two, specifying an executable program as the argument:

.Vb 1 gdb program .Ve

You can also start with both an executable program and a core file specified:

.Vb 1 gdb program core .Ve

You can, instead, specify a process \s-1ID\s0 as a second argument, if you want to debug a running process:

.Vb 2 gdb program 1234 gdb -p 1234 .Ve

would attach \s-1GDB\s0 to process 1234 (unless you also have a file named 1234; \s-1GDB\s0 does check for a core file first). With option -p you can omit the program filename.

Here are some of the most frequently needed \s-1GDB\s0 commands:

Item "break [file:]function" Set a breakpoint at function (in file). Item "run [arglist]" Start your program (with arglist, if specified). Item "bt" Backtrace: display the program stack. Item "print expr" Display the value of an expression. Item "c" Continue running your program (after stopping, e.g. at a breakpoint). Item "next" Execute next program line (after stopping); step over any function calls in the line. Item "edit [file:]function" look at the program line where it is presently stopped. Item "list [file:]function" type the text of the program in the vicinity of where it is presently stopped. Item "step" Execute next program line (after stopping); step into any function calls in the line. Item "help [name]" Show information about \s-1GDB\s0 command name, or general information about using \s-1GDB.\s0 Item "quit" Exit from \s-1GDB.\s0

For full details on \s-1GDB,\s0 see Using \s-1GDB: A\s0 Guide to the \s-1GNU\s0 Source-Level Debugger, by Richard M. Stallman and Roland H. Pesch. The same text is available online as the \*(C`gdb\*(C' entry in the \*(C`info\*(C' program.

Header "OPTIONS" Any arguments other than options specify an executable file and core file (or process \s-1ID\s0); that is, the first argument encountered with no associated option flag is equivalent to a -se option, and the second, if any, is equivalent to a -c option if it's the name of a file. Many options have both long and short forms; both are shown here. The long forms are also recognized if you truncate them, so long as enough of the option is present to be unambiguous. (If you prefer, you can flag option arguments with + rather than -, though we illustrate the more usual convention.)

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.

Item "-help"

0

Item "-h"

List all options, with brief explanations.

Item "-symbols=file"

0

Item "-s file"

Read symbol table from file file.

Item "-write" Enable writing into executable and core files. Item "-exec=file"

0

Item "-e file"

Use file file as the executable file to execute when appropriate, and for examining pure data in conjunction with a core dump.

Item "-se=file" Read symbol table from file file and use it as the executable file. Item "-core=file"

0

Item "-c file"

Use file file as a core dump to examine.

Item "-command=file"

0

Item "-x file"

Execute \s-1GDB\s0 commands from file file.

Item "-ex command" Execute given \s-1GDB\s0 command. Item "-directory=directory"

0

Item "-d directory"

Add directory to the path to search for source files.

Item "-nh" Do not execute commands from ~/.gdbinit. Item "-nx"

0

Item "-n"

Do not execute commands from any .gdbinit initialization files.

Item "-quiet"

0

Item "-q"

\*(L"Quiet\*(R". Do not print the introductory and copyright messages. These messages are also suppressed in batch mode.

Item "-batch" 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 \s-1GDB\s0 commands in the command files. .Sp Batch mode may be useful for running \s-1GDB\s0 as a filter, for example to download and run a program on another computer; in order to make this more useful, the message .Sp .Vb 1 Program exited normally. .Ve .Sp (which is ordinarily issued whenever a program running under \s-1GDB\s0 control terminates) is not issued when running in batch mode. Item "-cd=directory" Run \s-1GDB\s0 using directory as its working directory, instead of the current directory. Item "-fullname"

0

Item "-f"

Emacs sets this option when it runs \s-1GDB\s0 as a subprocess. It tells \s-1GDB\s0 to 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 \e032 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 \e032 characters as a signal to display the source code for the frame.

Item "-b bps" Set the line speed (baud rate or bits per second) of any serial interface used by \s-1GDB\s0 for remote debugging. Item "-tty=device" Run using device for your program's standard input and output. Header "SEE ALSO" The full documentation for \s-1GDB\s0 is maintained as a Texinfo manual. If the \*(C`info\*(C' and \*(C`gdb\*(C' programs and \s-1GDB\s0's Texinfo documentation are properly installed at your site, the command

.Vb 1 info gdb .Ve

should give you access to the complete manual.

\fIUsing \s-1GDB: A\s0 Guide to the \s-1GNU\s0 Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991.

Header "COPYRIGHT" Copyright (c) 1988-2019 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being \*(L"Free Software\*(R" and \*(L"Free Software Needs Free Documentation\*(R", with the Front-Cover Texts being \*(L"A \s-1GNU\s0 Manual,\*(R" and with the Back-Cover Texts as in (a) below.

(a) The \s-1FSF\s0's Back-Cover Text is: \*(L"You are free to copy and modify this \s-1GNU\s0 Manual. Buying copies from \s-1GNU\s0 Press supports the \s-1FSF\s0 in developing \s-1GNU\s0 and promoting software freedom.\*(R"