OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [gdb-5.0/] [gdb/] [gdb.1] - Diff between revs 105 and 1765

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 105 Rev 1765
.\" Copyright (c) 1991 Free Software Foundation
.\" Copyright (c) 1991 Free Software Foundation
.\" See section COPYING for conditions for redistribution
.\" See section COPYING for conditions for redistribution
.\" $Id: gdb.1,v 1.1.1.1 2001-05-18 11:03:25 markom Exp $
.\" $Id: gdb.1,v 1.1.1.1 2001-05-18 11:03:25 markom Exp $
.TH gdb 1 "4nov1991" "GNU Tools" "GNU Tools"
.TH gdb 1 "4nov1991" "GNU Tools" "GNU Tools"
.SH NAME
.SH NAME
gdb \- The GNU Debugger
gdb \- The GNU Debugger
.SH SYNOPSIS
.SH SYNOPSIS
.na
.na
.TP
.TP
.B gdb
.B gdb
.RB "[\|" \-help "\|]"
.RB "[\|" \-help "\|]"
.RB "[\|" \-nx "\|]"
.RB "[\|" \-nx "\|]"
.RB "[\|" \-q "\|]"
.RB "[\|" \-q "\|]"
.RB "[\|" \-batch "\|]"
.RB "[\|" \-batch "\|]"
.RB "[\|" \-cd=\c
.RB "[\|" \-cd=\c
.I dir\c
.I dir\c
\|]
\|]
.RB "[\|" \-f "\|]"
.RB "[\|" \-f "\|]"
.RB "[\|" "\-b\ "\c
.RB "[\|" "\-b\ "\c
.IR bps "\|]"
.IR bps "\|]"
.RB "[\|" "\-tty="\c
.RB "[\|" "\-tty="\c
.IR dev "\|]"
.IR dev "\|]"
.RB "[\|" "\-s "\c
.RB "[\|" "\-s "\c
.I symfile\c
.I symfile\c
\&\|]
\&\|]
.RB "[\|" "\-e "\c
.RB "[\|" "\-e "\c
.I prog\c
.I prog\c
\&\|]
\&\|]
.RB "[\|" "\-se "\c
.RB "[\|" "\-se "\c
.I prog\c
.I prog\c
\&\|]
\&\|]
.RB "[\|" "\-c "\c
.RB "[\|" "\-c "\c
.I core\c
.I core\c
\&\|]
\&\|]
.RB "[\|" "\-x "\c
.RB "[\|" "\-x "\c
.I cmds\c
.I cmds\c
\&\|]
\&\|]
.RB "[\|" "\-d "\c
.RB "[\|" "\-d "\c
.I dir\c
.I dir\c
\&\|]
\&\|]
.RB "[\|" \c
.RB "[\|" \c
.I prog\c
.I prog\c
.RB "[\|" \c
.RB "[\|" \c
.IR core \||\| procID\c
.IR core \||\| procID\c
\&\|]\&\|]
\&\|]\&\|]
.ad b
.ad b
.SH DESCRIPTION
.SH DESCRIPTION
The purpose of a debugger such as GDB is to allow you to see what is
The purpose of a debugger such as GDB is to allow you to see what is
going on ``inside'' another program while it executes\(em\&or what another
going on ``inside'' another program while it executes\(em\&or what another
program was doing at the moment it crashed.
program was doing at the moment it crashed.
GDB can do four main kinds of things (plus other things in support of
GDB can do four main kinds of things (plus other things in support of
these) to help you catch bugs in the act:
these) to help you catch bugs in the act:
.TP
.TP
\ \ \ \(bu
\ \ \ \(bu
Start your program, specifying anything that might affect its behavior.
Start your program, specifying anything that might affect its behavior.
.TP
.TP
\ \ \ \(bu
\ \ \ \(bu
Make your program stop on specified conditions.
Make your program stop on specified conditions.
.TP
.TP
\ \ \ \(bu
\ \ \ \(bu
Examine what has happened, when your program has stopped.
Examine what has happened, when your program has stopped.
.TP
.TP
\ \ \ \(bu
\ \ \ \(bu
Change things in your program, so you can experiment with correcting the
Change things in your program, so you can experiment with correcting the
effects of one bug and go on to learn about another.
effects of one bug and go on to learn about another.
.PP
.PP
You can use GDB to debug programs written in C, C++, and Modula-2.
You can use GDB to debug programs written in C, C++, and Modula-2.
Fortran support will be added when a GNU Fortran compiler is ready.
Fortran support will be added when a GNU Fortran compiler is ready.
GDB is invoked with the shell command \c
GDB is invoked with the shell command \c
.B gdb\c
.B gdb\c
\&.  Once started, it reads
\&.  Once started, it reads
commands from the terminal until you tell it to exit with the GDB
commands from the terminal until you tell it to exit with the GDB
command \c
command \c
.B quit\c
.B quit\c
\&.  You can get online help from \c
\&.  You can get online help from \c
.B gdb\c
.B gdb\c
\& itself
\& itself
by using the command \c
by using the command \c
.B help\c
.B help\c
\&.
\&.
You can run \c
You can run \c
.B gdb\c
.B gdb\c
\& with no arguments or options; but the most
\& with no arguments or options; but the most
usual way to start GDB is with one argument or two, specifying an
usual way to start GDB is with one argument or two, specifying an
executable program as the argument:
executable program as the argument:
.sp
.sp
.br
.br
gdb\ program
gdb\ program
.br
.br
.sp
.sp
You can also start with both an executable program and a core file specified:
You can also start with both an executable program and a core file specified:
.sp
.sp
.br
.br
gdb\ program\ core
gdb\ program\ core
.br
.br
.sp
.sp
You can, instead, specify a process ID as a second argument, if you want
You can, instead, specify a process ID as a second argument, if you want
to debug a running process:
to debug a running process:
.sp
.sp
.br
.br
gdb\ program\ 1234
gdb\ program\ 1234
.br
.br
.sp
.sp
would attach GDB to process \c
would attach GDB to process \c
.B 1234\c
.B 1234\c
\& (unless you also have a file
\& (unless you also have a file
named `\|\c
named `\|\c
.B 1234\c
.B 1234\c
\&\|'; GDB does check for a core file first).
\&\|'; GDB does check for a core file first).
Here are some of the most frequently needed GDB commands:
Here are some of the most frequently needed GDB commands:
.TP
.TP
.B break \fR[\|\fIfile\fB:\fR\|]\fIfunction
.B break \fR[\|\fIfile\fB:\fR\|]\fIfunction
\&
\&
Set a breakpoint at \c
Set a breakpoint at \c
.I function\c
.I function\c
\& (in \c
\& (in \c
.I file\c
.I file\c
\&).
\&).
.TP
.TP
.B run \fR[\|\fIarglist\fR\|]
.B run \fR[\|\fIarglist\fR\|]
Start your program (with \c
Start your program (with \c
.I arglist\c
.I arglist\c
\&, if specified).
\&, if specified).
.TP
.TP
.B bt
.B bt
Backtrace: display the program stack.
Backtrace: display the program stack.
.TP
.TP
.BI print " expr"\c
.BI print " expr"\c
\&
\&
Display the value of an expression.
Display the value of an expression.
.TP
.TP
.B c
.B c
Continue running your program (after stopping, e.g. at a breakpoint).
Continue running your program (after stopping, e.g. at a breakpoint).
.TP
.TP
.B next
.B next
Execute next program line (after stopping); step \c
Execute next program line (after stopping); step \c
.I over\c
.I over\c
\& any
\& any
function calls in the line.
function calls in the line.
.TP
.TP
.B step
.B step
Execute next program line (after stopping); step \c
Execute next program line (after stopping); step \c
.I into\c
.I into\c
\& any
\& any
function calls in the line.
function calls in the line.
.TP
.TP
.B help \fR[\|\fIname\fR\|]
.B help \fR[\|\fIname\fR\|]
Show information about GDB command \c
Show information about GDB command \c
.I name\c
.I name\c
\&, or general information
\&, or general information
about using GDB.
about using GDB.
.TP
.TP
.B quit
.B quit
Exit from GDB.
Exit from GDB.
.PP
.PP
For full details on GDB, see \c
For full details on GDB, see \c
.I
.I
Using GDB: A Guide to the GNU Source-Level Debugger\c
Using GDB: A Guide to the GNU Source-Level Debugger\c
\&, by Richard M. Stallman and Roland H. Pesch.  The same text is available online
\&, by Richard M. Stallman and Roland H. Pesch.  The same text is available online
as the \c
as the \c
.B gdb\c
.B gdb\c
\& entry in the \c
\& entry in the \c
.B info\c
.B info\c
\& program.
\& program.
.SH OPTIONS
.SH OPTIONS
Any arguments other than options specify an executable
Any arguments other than options specify an executable
file and core file (or process ID); that is, the first argument
file and core file (or process ID); that is, the first argument
encountered with no
encountered with no
associated option flag is equivalent to a `\|\c
associated option flag is equivalent to a `\|\c
.B \-se\c
.B \-se\c
\&\|' option, and the
\&\|' option, and the
second, if any, is equivalent to a `\|\c
second, if any, is equivalent to a `\|\c
.B \-c\c
.B \-c\c
\&\|' option if it's the name of a file.  Many options have
\&\|' 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
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
recognized if you truncate them, so long as enough of the option is
present to be unambiguous.  (If you prefer, you can flag option
present to be unambiguous.  (If you prefer, you can flag option
arguments with `\|\c
arguments with `\|\c
.B +\c
.B +\c
\&\|' rather than `\|\c
\&\|' rather than `\|\c
.B \-\c
.B \-\c
\&\|', though we illustrate the
\&\|', though we illustrate the
more usual convention.)
more usual convention.)
All the options and command line arguments you give are processed
All the options and command line arguments you give are processed
in sequential order.  The order makes a difference when the
in sequential order.  The order makes a difference when the
`\|\c
`\|\c
.B \-x\c
.B \-x\c
\&\|' option is used.
\&\|' option is used.
.TP
.TP
.B \-help
.B \-help
.TP
.TP
.B \-h
.B \-h
List all options, with brief explanations.
List all options, with brief explanations.
.TP
.TP
.BI "\-symbols=" "file"\c
.BI "\-symbols=" "file"\c
.TP
.TP
.BI "\-s " "file"\c
.BI "\-s " "file"\c
\&
\&
Read symbol table from file \c
Read symbol table from file \c
.I file\c
.I file\c
\&.
\&.
.TP
.TP
.B \-write
.B \-write
Enable writing into executable and core files.
Enable writing into executable and core files.
.TP
.TP
.BI "\-exec=" "file"\c
.BI "\-exec=" "file"\c
.TP
.TP
.BI "\-e " "file"\c
.BI "\-e " "file"\c
\&
\&
Use file \c
Use file \c
.I file\c
.I file\c
\& as the executable file to execute when
\& as the executable file to execute when
appropriate, and for examining pure data in conjunction with a core
appropriate, and for examining pure data in conjunction with a core
dump.
dump.
.TP
.TP
.BI "\-se=" "file"\c
.BI "\-se=" "file"\c
\&
\&
Read symbol table from file \c
Read symbol table from file \c
.I file\c
.I file\c
\& and use it as the executable
\& and use it as the executable
file.
file.
.TP
.TP
.BI "\-core=" "file"\c
.BI "\-core=" "file"\c
.TP
.TP
.BI "\-c " "file"\c
.BI "\-c " "file"\c
\&
\&
Use file \c
Use file \c
.I file\c
.I file\c
\& as a core dump to examine.
\& as a core dump to examine.
.TP
.TP
.BI "\-command=" "file"\c
.BI "\-command=" "file"\c
.TP
.TP
.BI "\-x " "file"\c
.BI "\-x " "file"\c
\&
\&
Execute GDB commands from file \c
Execute GDB commands from file \c
.I file\c
.I file\c
\&.
\&.
.TP
.TP
.BI "\-directory=" "directory"\c
.BI "\-directory=" "directory"\c
.TP
.TP
.BI "\-d " "directory"\c
.BI "\-d " "directory"\c
\&
\&
Add \c
Add \c
.I directory\c
.I directory\c
\& to the path to search for source files.
\& to the path to search for source files.
.PP
.PP
.TP
.TP
.B \-nx
.B \-nx
.TP
.TP
.B \-n
.B \-n
Do not execute commands from any `\|\c
Do not execute commands from any `\|\c
.B .gdbinit\c
.B .gdbinit\c
\&\|' initialization files.
\&\|' initialization files.
Normally, the commands in these files are executed after all the
Normally, the commands in these files are executed after all the
command options and arguments have been processed.
command options and arguments have been processed.
.TP
.TP
.B \-quiet
.B \-quiet
.TP
.TP
.B \-q
.B \-q
``Quiet''.  Do not print the introductory and copyright messages.  These
``Quiet''.  Do not print the introductory and copyright messages.  These
messages are also suppressed in batch mode.
messages are also suppressed in batch mode.
.TP
.TP
.B \-batch
.B \-batch
Run in batch mode.  Exit with status \c
Run in batch mode.  Exit with status \c
.B 0\c
.B 0\c
\& after processing all the command
\& after processing all the command
files specified with `\|\c
files specified with `\|\c
.B \-x\c
.B \-x\c
\&\|' (and `\|\c
\&\|' (and `\|\c
.B .gdbinit\c
.B .gdbinit\c
\&\|', if not inhibited).
\&\|', if not inhibited).
Exit with nonzero status if an error occurs in executing the GDB
Exit with nonzero status if an error occurs in executing the GDB
commands in the command files.
commands in the command files.
Batch mode may be useful for running GDB as a filter, for example to
Batch mode may be useful for running GDB as a filter, for example to
download and run a program on another computer; in order to make this
download and run a program on another computer; in order to make this
more useful, the message
more useful, the message
.sp
.sp
.br
.br
Program\ exited\ normally.
Program\ exited\ normally.
.br
.br
.sp
.sp
(which is ordinarily issued whenever a program running under GDB control
(which is ordinarily issued whenever a program running under GDB control
terminates) is not issued when running in batch mode.
terminates) is not issued when running in batch mode.
.TP
.TP
.BI "\-cd=" "directory"\c
.BI "\-cd=" "directory"\c
\&
\&
Run GDB using \c
Run GDB using \c
.I directory\c
.I directory\c
\& as its working directory,
\& as its working directory,
instead of the current directory.
instead of the current directory.
.TP
.TP
.B \-fullname
.B \-fullname
.TP
.TP
.B \-f
.B \-f
Emacs sets this option when it runs GDB as a subprocess.  It tells GDB
Emacs sets this option when it runs GDB as a subprocess.  It tells GDB
to output the full file name and line number in a standard,
to output the full file name and line number in a standard,
recognizable fashion each time a stack frame is displayed (which
recognizable fashion each time a stack frame is displayed (which
includes each time the program stops).  This recognizable format looks
includes each time the program stops).  This recognizable format looks
like two `\|\c
like two `\|\c
.B \032\c
.B \032\c
\&\|' characters, followed by the file name, line number
\&\|' characters, followed by the file name, line number
and character position separated by colons, and a newline.  The
and character position separated by colons, and a newline.  The
Emacs-to-GDB interface program uses the two `\|\c
Emacs-to-GDB interface program uses the two `\|\c
.B \032\c
.B \032\c
\&\|' characters as
\&\|' characters as
a signal to display the source code for the frame.
a signal to display the source code for the frame.
.TP
.TP
.BI "\-b " "bps"\c
.BI "\-b " "bps"\c
\&
\&
Set the line speed (baud rate or bits per second) of any serial
Set the line speed (baud rate or bits per second) of any serial
interface used by GDB for remote debugging.
interface used by GDB for remote debugging.
.TP
.TP
.BI "\-tty=" "device"\c
.BI "\-tty=" "device"\c
\&
\&
Run using \c
Run using \c
.I device\c
.I device\c
\& for your program's standard input and output.
\& for your program's standard input and output.
.PP
.PP
.SH "SEE ALSO"
.SH "SEE ALSO"
.RB "`\|" gdb "\|'"
.RB "`\|" gdb "\|'"
entry in
entry in
.B info\c
.B info\c
\&;
\&;
.I
.I
Using GDB: A Guide to the GNU Source-Level Debugger\c
Using GDB: A Guide to the GNU Source-Level Debugger\c
, Richard M. Stallman and Roland H. Pesch, July 1991.
, Richard M. Stallman and Roland H. Pesch, July 1991.
.SH COPYING
.SH COPYING
Copyright (c) 1991 Free Software Foundation, Inc.
Copyright (c) 1991 Free Software Foundation, Inc.
.PP
.PP
Permission is granted to make and distribute verbatim copies of
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
this manual provided the copyright notice and this permission notice
are preserved on all copies.
are preserved on all copies.
.PP
.PP
Permission is granted to copy and distribute modified versions of this
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
permission notice identical to this one.
.PP
.PP
Permission is granted to copy and distribute translations of this
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
manual into another language, under the above conditions for modified
versions, except that this permission notice may be included in
versions, except that this permission notice may be included in
translations approved by the Free Software Foundation instead of in
translations approved by the Free Software Foundation instead of in
the original English.
the original English.
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.