README for gdb-7.1 release
|
README for gdb-7.1 release
|
Updated 18, March, 2010
|
Updated 18, March, 2010
|
|
|
This is GDB, the GNU source-level debugger.
|
This is GDB, the GNU source-level debugger.
|
|
|
A summary of new features is in the file `gdb/NEWS'.
|
A summary of new features is in the file `gdb/NEWS'.
|
|
|
Check the GDB home page at http://www.gnu.org/software/gdb/ for up to
|
Check the GDB home page at http://www.gnu.org/software/gdb/ for up to
|
date release information, mailing list links and archives, etc.
|
date release information, mailing list links and archives, etc.
|
|
|
The file `gdb/PROBLEMS' contains information on problems identified
|
The file `gdb/PROBLEMS' contains information on problems identified
|
late in the release cycle. GDB's bug tracking data base at
|
late in the release cycle. GDB's bug tracking data base at
|
http://www.gnu.org/software/gdb/bugs/ contains a more complete list of
|
http://www.gnu.org/software/gdb/bugs/ contains a more complete list of
|
bugs.
|
bugs.
|
|
|
|
|
Unpacking and Installation -- quick overview
|
Unpacking and Installation -- quick overview
|
==========================
|
==========================
|
|
|
In this release, the GDB debugger sources, the generic GNU include
|
In this release, the GDB debugger sources, the generic GNU include
|
files, the BFD ("binary file description") library, the readline
|
files, the BFD ("binary file description") library, the readline
|
library, and other libraries all have directories of their own
|
library, and other libraries all have directories of their own
|
underneath the gdb-7.1 directory. The idea is that a variety of GNU
|
underneath the gdb-7.1 directory. The idea is that a variety of GNU
|
tools can share a common copy of these things. Be aware of variation
|
tools can share a common copy of these things. Be aware of variation
|
over time--for example don't try to build gdb with a copy of bfd from
|
over time--for example don't try to build gdb with a copy of bfd from
|
a release other than the gdb release (such as a binutils release),
|
a release other than the gdb release (such as a binutils release),
|
especially if the releases are more than a few weeks apart.
|
especially if the releases are more than a few weeks apart.
|
Configuration scripts and makefiles exist to cruise up and down this
|
Configuration scripts and makefiles exist to cruise up and down this
|
directory tree and automatically build all the pieces in the right
|
directory tree and automatically build all the pieces in the right
|
order.
|
order.
|
|
|
When you unpack the gdb-7.1.tar.gz file, you'll find a directory
|
When you unpack the gdb-7.1.tar.gz file, you'll find a directory
|
called `gdb-7.1', which contains:
|
called `gdb-7.1', which contains:
|
|
|
COPYING config-ml.in gettext.m4 ltconfig sim
|
COPYING config-ml.in gettext.m4 ltconfig sim
|
COPYING.LIB config.guess include ltmain.sh src-release
|
COPYING.LIB config.guess include ltmain.sh src-release
|
Makefile.def config.sub install-sh md5.sum symlink-tree
|
Makefile.def config.sub install-sh md5.sum symlink-tree
|
Makefile.in configure libiberty missing texinfo
|
Makefile.in configure libiberty missing texinfo
|
Makefile.tpl configure.in libtool.m4 mkinstalldirs ylwrap
|
Makefile.tpl configure.in libtool.m4 mkinstalldirs ylwrap
|
README djunpack.bat ltcf-c.sh move-if-change
|
README djunpack.bat ltcf-c.sh move-if-change
|
bfd etc ltcf-cxx.sh opcodes
|
bfd etc ltcf-cxx.sh opcodes
|
config gdb ltcf-gcj.sh readline
|
config gdb ltcf-gcj.sh readline
|
|
|
You can build GDB right in the source directory:
|
You can build GDB right in the source directory:
|
|
|
cd gdb-7.1
|
cd gdb-7.1
|
./configure
|
./configure
|
make
|
make
|
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
|
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
|
|
|
However, we recommend that an empty directory be used instead.
|
However, we recommend that an empty directory be used instead.
|
This way you do not clutter your source tree with binary files
|
This way you do not clutter your source tree with binary files
|
and will be able to create different builds with different
|
and will be able to create different builds with different
|
configuration options.
|
configuration options.
|
|
|
You can build GDB in any empty build directory:
|
You can build GDB in any empty build directory:
|
|
|
mkdir build
|
mkdir build
|
cd build
|
cd build
|
/gdb-7.1/configure
|
/gdb-7.1/configure
|
make
|
make
|
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
|
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
|
|
|
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
|
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
|
different; see the file gdb-7.1/gdb/config/djgpp/README for details.)
|
different; see the file gdb-7.1/gdb/config/djgpp/README for details.)
|
|
|
This will configure and build all the libraries as well as GDB. If
|
This will configure and build all the libraries as well as GDB. If
|
`configure' can't determine your system type, specify one as its
|
`configure' can't determine your system type, specify one as its
|
argument, e.g., `./configure sun4' or `./configure decstation'.
|
argument, e.g., `./configure sun4' or `./configure decstation'.
|
|
|
Make sure that your 'configure' line ends in 'gdb-7.1/configure':
|
Make sure that your 'configure' line ends in 'gdb-7.1/configure':
|
|
|
/berman/migchain/source/gdb-7.1/configure # RIGHT
|
/berman/migchain/source/gdb-7.1/configure # RIGHT
|
/berman/migchain/source/gdb-7.1/gdb/configure # WRONG
|
/berman/migchain/source/gdb-7.1/gdb/configure # WRONG
|
|
|
The gdb package contains several subdirectories, such as 'gdb',
|
The gdb package contains several subdirectories, such as 'gdb',
|
'bfd', and 'readline'. If your 'configure' line ends in
|
'bfd', and 'readline'. If your 'configure' line ends in
|
'gdb-7.1/gdb/configure', then you are configuring only the gdb
|
'gdb-7.1/gdb/configure', then you are configuring only the gdb
|
subdirectory, not the whole gdb package. This leads to build errors
|
subdirectory, not the whole gdb package. This leads to build errors
|
such as:
|
such as:
|
|
|
make: *** No rule to make target `../bfd/bfd.h', needed by `gdb.o'. Stop.
|
make: *** No rule to make target `../bfd/bfd.h', needed by `gdb.o'. Stop.
|
|
|
If you get other compiler errors during this stage, see the `Reporting
|
If you get other compiler errors during this stage, see the `Reporting
|
Bugs' section below; there are a few known problems.
|
Bugs' section below; there are a few known problems.
|
|
|
GDB requires an ISO C (ANSI C) compiler. If you do not have an ISO
|
GDB requires an ISO C (ANSI C) compiler. If you do not have an ISO
|
C compiler for your system, you may be able to download and install
|
C compiler for your system, you may be able to download and install
|
the GNU CC compiler. It is available via anonymous FTP from the
|
the GNU CC compiler. It is available via anonymous FTP from the
|
directory `ftp://ftp.gnu.org/pub/gnu/gcc'. GDB also requires an ISO
|
directory `ftp://ftp.gnu.org/pub/gnu/gcc'. GDB also requires an ISO
|
C standard library. The GDB remote server, gdbserver, builds with some
|
C standard library. The GDB remote server, gdbserver, builds with some
|
non-ISO standard libraries - e.g. for Windows CE.
|
non-ISO standard libraries - e.g. for Windows CE.
|
|
|
GDB uses Expat, an XML parsing library, to implement some target-specific
|
GDB uses Expat, an XML parsing library, to implement some target-specific
|
features. Expat will be linked in if it is available at build time, or
|
features. Expat will be linked in if it is available at build time, or
|
those features will be disabled. The latest version of Expat should be
|
those features will be disabled. The latest version of Expat should be
|
available from `http://expat.sourceforge.net'.
|
available from `http://expat.sourceforge.net'.
|
|
|
GDB can be used as a cross-debugger, running on a machine of one
|
GDB can be used as a cross-debugger, running on a machine of one
|
type while debugging a program running on a machine of another type.
|
type while debugging a program running on a machine of another type.
|
See below.
|
See below.
|
|
|
|
|
More Documentation
|
More Documentation
|
******************
|
******************
|
|
|
All the documentation for GDB comes as part of the machine-readable
|
All the documentation for GDB comes as part of the machine-readable
|
distribution. The documentation is written in Texinfo format, which
|
distribution. The documentation is written in Texinfo format, which
|
is a documentation system that uses a single source file to produce
|
is a documentation system that uses a single source file to produce
|
both on-line information and a printed manual. You can use one of the
|
both on-line information and a printed manual. You can use one of the
|
Info formatting commands to create the on-line version of the
|
Info formatting commands to create the on-line version of the
|
documentation and TeX (or `texi2roff') to typeset the printed version.
|
documentation and TeX (or `texi2roff') to typeset the printed version.
|
|
|
GDB includes an already formatted copy of the on-line Info version
|
GDB includes an already formatted copy of the on-line Info version
|
of this manual in the `gdb/doc' subdirectory. The main Info file is
|
of this manual in the `gdb/doc' subdirectory. The main Info file is
|
`gdb-7.1/gdb/doc/gdb.info', and it refers to subordinate files
|
`gdb-7.1/gdb/doc/gdb.info', and it refers to subordinate files
|
matching `gdb.info*' in the same directory. If necessary, you can
|
matching `gdb.info*' in the same directory. If necessary, you can
|
print out these files, or read them with any editor; but they are
|
print out these files, or read them with any editor; but they are
|
easier to read using the `info' subsystem in GNU Emacs or the
|
easier to read using the `info' subsystem in GNU Emacs or the
|
standalone `info' program, available as part of the GNU Texinfo
|
standalone `info' program, available as part of the GNU Texinfo
|
distribution.
|
distribution.
|
|
|
If you want to format these Info files yourself, you need one of the
|
If you want to format these Info files yourself, you need one of the
|
Info formatting programs, such as `texinfo-format-buffer' or
|
Info formatting programs, such as `texinfo-format-buffer' or
|
`makeinfo'.
|
`makeinfo'.
|
|
|
If you have `makeinfo' installed, and are in the top level GDB
|
If you have `makeinfo' installed, and are in the top level GDB
|
source directory (`gdb-7.1', in the case of version 7.1), you can make
|
source directory (`gdb-7.1', in the case of version 7.1), you can make
|
the Info file by typing:
|
the Info file by typing:
|
|
|
cd gdb/doc
|
cd gdb/doc
|
make info
|
make info
|
|
|
If you want to typeset and print copies of this manual, you need
|
If you want to typeset and print copies of this manual, you need
|
TeX, a program to print its DVI output files, and `texinfo.tex', the
|
TeX, a program to print its DVI output files, and `texinfo.tex', the
|
Texinfo definitions file. This file is included in the GDB
|
Texinfo definitions file. This file is included in the GDB
|
distribution, in the directory `gdb-7.1/texinfo'.
|
distribution, in the directory `gdb-7.1/texinfo'.
|
|
|
TeX is a typesetting program; it does not print files directly, but
|
TeX is a typesetting program; it does not print files directly, but
|
produces output files called DVI files. To print a typeset document,
|
produces output files called DVI files. To print a typeset document,
|
you need a program to print DVI files. If your system has TeX
|
you need a program to print DVI files. If your system has TeX
|
installed, chances are it has such a program. The precise command to
|
installed, chances are it has such a program. The precise command to
|
use depends on your system; `lpr -d' is common; another (for PostScript
|
use depends on your system; `lpr -d' is common; another (for PostScript
|
devices) is `dvips'. The DVI print command may require a file name
|
devices) is `dvips'. The DVI print command may require a file name
|
without any extension or a `.dvi' extension.
|
without any extension or a `.dvi' extension.
|
|
|
TeX also requires a macro definitions file called `texinfo.tex'.
|
TeX also requires a macro definitions file called `texinfo.tex'.
|
This file tells TeX how to typeset a document written in Texinfo
|
This file tells TeX how to typeset a document written in Texinfo
|
format. On its own, TeX cannot read, much less typeset a Texinfo file.
|
format. On its own, TeX cannot read, much less typeset a Texinfo file.
|
`texinfo.tex' is distributed with GDB and is located in the
|
`texinfo.tex' is distributed with GDB and is located in the
|
`gdb-7.1/texinfo' directory.
|
`gdb-7.1/texinfo' directory.
|
|
|
If you have TeX and a DVI printer program installed, you can typeset
|
If you have TeX and a DVI printer program installed, you can typeset
|
and print this manual. First switch to the the `gdb' subdirectory of
|
and print this manual. First switch to the the `gdb' subdirectory of
|
the main source directory (for example, to `gdb-7.1/gdb') and then type:
|
the main source directory (for example, to `gdb-7.1/gdb') and then type:
|
|
|
make doc/gdb.dvi
|
make doc/gdb.dvi
|
|
|
If you prefer to have the manual in PDF format, type this from the
|
If you prefer to have the manual in PDF format, type this from the
|
`gdb/doc' subdirectory of the main source directory:
|
`gdb/doc' subdirectory of the main source directory:
|
|
|
make gdb.pdf
|
make gdb.pdf
|
|
|
For this to work, you will need the PDFTeX package to be installed.
|
For this to work, you will need the PDFTeX package to be installed.
|
|
|
|
|
Installing GDB
|
Installing GDB
|
**************
|
**************
|
|
|
GDB comes with a `configure' script that automates the process of
|
GDB comes with a `configure' script that automates the process of
|
preparing GDB for installation; you can then use `make' to build the
|
preparing GDB for installation; you can then use `make' to build the
|
`gdb' program.
|
`gdb' program.
|
|
|
The GDB distribution includes all the source code you need for GDB in
|
The GDB distribution includes all the source code you need for GDB in
|
a single directory, whose name is usually composed by appending the
|
a single directory, whose name is usually composed by appending the
|
version number to `gdb'.
|
version number to `gdb'.
|
|
|
For example, the GDB version 7.1 distribution is in the `gdb-7.1'
|
For example, the GDB version 7.1 distribution is in the `gdb-7.1'
|
directory. That directory contains:
|
directory. That directory contains:
|
|
|
`gdb-7.1/{COPYING,COPYING.LIB}'
|
`gdb-7.1/{COPYING,COPYING.LIB}'
|
Standard GNU license files. Please read them.
|
Standard GNU license files. Please read them.
|
|
|
`gdb-7.1/bfd'
|
`gdb-7.1/bfd'
|
source for the Binary File Descriptor library
|
source for the Binary File Descriptor library
|
|
|
`gdb-7.1/config*'
|
`gdb-7.1/config*'
|
script for configuring GDB, along with other support files
|
script for configuring GDB, along with other support files
|
|
|
`gdb-7.1/gdb'
|
`gdb-7.1/gdb'
|
the source specific to GDB itself
|
the source specific to GDB itself
|
|
|
`gdb-7.1/include'
|
`gdb-7.1/include'
|
GNU include files
|
GNU include files
|
|
|
`gdb-7.1/libiberty'
|
`gdb-7.1/libiberty'
|
source for the `-liberty' free software library
|
source for the `-liberty' free software library
|
|
|
`gdb-7.1/opcodes'
|
`gdb-7.1/opcodes'
|
source for the library of opcode tables and disassemblers
|
source for the library of opcode tables and disassemblers
|
|
|
`gdb-7.1/readline'
|
`gdb-7.1/readline'
|
source for the GNU command-line interface
|
source for the GNU command-line interface
|
NOTE: The readline library is compiled for use by GDB, but will
|
NOTE: The readline library is compiled for use by GDB, but will
|
not be installed on your system when "make install" is issued.
|
not be installed on your system when "make install" is issued.
|
|
|
`gdb-7.1/sim'
|
`gdb-7.1/sim'
|
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
|
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
|
|
|
`gdb-7.1/texinfo'
|
`gdb-7.1/texinfo'
|
The `texinfo.tex' file, which you need in order to make a printed
|
The `texinfo.tex' file, which you need in order to make a printed
|
manual using TeX.
|
manual using TeX.
|
|
|
`gdb-7.1/etc'
|
`gdb-7.1/etc'
|
Coding standards, useful files for editing GDB, and other
|
Coding standards, useful files for editing GDB, and other
|
miscellanea.
|
miscellanea.
|
|
|
Note: the following instructions are for building GDB on Unix or
|
Note: the following instructions are for building GDB on Unix or
|
Unix-like systems. Instructions for building with DJGPP for
|
Unix-like systems. Instructions for building with DJGPP for
|
MS-DOS/MS-Windows are in the file gdb/config/djgpp/README.
|
MS-DOS/MS-Windows are in the file gdb/config/djgpp/README.
|
|
|
The simplest way to configure and build GDB is to run `configure'
|
The simplest way to configure and build GDB is to run `configure'
|
from the `gdb-VERSION-NUMBER' source directory, which in this example
|
from the `gdb-VERSION-NUMBER' source directory, which in this example
|
is the `gdb-7.1' directory.
|
is the `gdb-7.1' directory.
|
|
|
First switch to the `gdb-VERSION-NUMBER' source directory if you are
|
First switch to the `gdb-VERSION-NUMBER' source directory if you are
|
not already in it; then run `configure'.
|
not already in it; then run `configure'.
|
|
|
For example:
|
For example:
|
|
|
cd gdb-7.1
|
cd gdb-7.1
|
./configure
|
./configure
|
make
|
make
|
|
|
Running `configure' followed by `make' builds the `bfd',
|
Running `configure' followed by `make' builds the `bfd',
|
`readline', `mmalloc', and `libiberty' libraries, then `gdb' itself.
|
`readline', `mmalloc', and `libiberty' libraries, then `gdb' itself.
|
The configured source files, and the binaries, are left in the
|
The configured source files, and the binaries, are left in the
|
corresponding source directories.
|
corresponding source directories.
|
|
|
`configure' is a Bourne-shell (`/bin/sh') script; if your system
|
`configure' is a Bourne-shell (`/bin/sh') script; if your system
|
does not recognize this automatically when you run a different shell,
|
does not recognize this automatically when you run a different shell,
|
you may need to run `sh' on it explicitly:
|
you may need to run `sh' on it explicitly:
|
|
|
sh configure
|
sh configure
|
|
|
If you run `configure' from a directory that contains source
|
If you run `configure' from a directory that contains source
|
directories for multiple libraries or programs, such as the `gdb-7.1'
|
directories for multiple libraries or programs, such as the `gdb-7.1'
|
source directory for version 7.1, `configure' creates configuration
|
source directory for version 7.1, `configure' creates configuration
|
files for every directory level underneath (unless you tell it not to,
|
files for every directory level underneath (unless you tell it not to,
|
with the `--norecursion' option).
|
with the `--norecursion' option).
|
|
|
You can run the `configure' script from any of the subordinate
|
You can run the `configure' script from any of the subordinate
|
directories in the GDB distribution, if you only want to configure that
|
directories in the GDB distribution, if you only want to configure that
|
subdirectory; but be sure to specify a path to it.
|
subdirectory; but be sure to specify a path to it.
|
|
|
For example, with version 7.1, type the following to configure only
|
For example, with version 7.1, type the following to configure only
|
the `bfd' subdirectory:
|
the `bfd' subdirectory:
|
|
|
cd gdb-7.1/bfd
|
cd gdb-7.1/bfd
|
../configure
|
../configure
|
|
|
You can install `gdb' anywhere; it has no hardwired paths. However,
|
You can install `gdb' anywhere; it has no hardwired paths. However,
|
you should make sure that the shell on your path (named by the `SHELL'
|
you should make sure that the shell on your path (named by the `SHELL'
|
environment variable) is publicly readable. Remember that GDB uses the
|
environment variable) is publicly readable. Remember that GDB uses the
|
shell to start your program--some systems refuse to let GDB debug child
|
shell to start your program--some systems refuse to let GDB debug child
|
processes whose programs are not readable.
|
processes whose programs are not readable.
|
|
|
|
|
Compiling GDB in another directory
|
Compiling GDB in another directory
|
==================================
|
==================================
|
|
|
If you want to run GDB versions for several host or target machines,
|
If you want to run GDB versions for several host or target machines,
|
you need a different `gdb' compiled for each combination of host and
|
you need a different `gdb' compiled for each combination of host and
|
target. `configure' is designed to make this easy by allowing you to
|
target. `configure' is designed to make this easy by allowing you to
|
generate each configuration in a separate subdirectory, rather than in
|
generate each configuration in a separate subdirectory, rather than in
|
the source directory. If your `make' program handles the `VPATH'
|
the source directory. If your `make' program handles the `VPATH'
|
feature correctly (GNU `make' and SunOS 'make' are two that should),
|
feature correctly (GNU `make' and SunOS 'make' are two that should),
|
running `make' in each of these directories builds the `gdb' program
|
running `make' in each of these directories builds the `gdb' program
|
specified there.
|
specified there.
|
|
|
To build `gdb' in a separate directory, run `configure' with the
|
To build `gdb' in a separate directory, run `configure' with the
|
`--srcdir' option to specify where to find the source. (You also need
|
`--srcdir' option to specify where to find the source. (You also need
|
to specify a path to find `configure' itself from your working
|
to specify a path to find `configure' itself from your working
|
directory. If the path to `configure' would be the same as the
|
directory. If the path to `configure' would be the same as the
|
argument to `--srcdir', you can leave out the `--srcdir' option; it
|
argument to `--srcdir', you can leave out the `--srcdir' option; it
|
will be assumed.)
|
will be assumed.)
|
|
|
For example, with version 7.1, you can build GDB in a separate
|
For example, with version 7.1, you can build GDB in a separate
|
directory for a Sun 4 like this:
|
directory for a Sun 4 like this:
|
|
|
cd gdb-7.1
|
cd gdb-7.1
|
mkdir ../gdb-sun4
|
mkdir ../gdb-sun4
|
cd ../gdb-sun4
|
cd ../gdb-sun4
|
../gdb-7.1/configure
|
../gdb-7.1/configure
|
make
|
make
|
|
|
When `configure' builds a configuration using a remote source
|
When `configure' builds a configuration using a remote source
|
directory, it creates a tree for the binaries with the same structure
|
directory, it creates a tree for the binaries with the same structure
|
(and using the same names) as the tree under the source directory. In
|
(and using the same names) as the tree under the source directory. In
|
the example, you'd find the Sun 4 library `libiberty.a' in the
|
the example, you'd find the Sun 4 library `libiberty.a' in the
|
directory `gdb-sun4/libiberty', and GDB itself in `gdb-sun4/gdb'.
|
directory `gdb-sun4/libiberty', and GDB itself in `gdb-sun4/gdb'.
|
|
|
One popular reason to build several GDB configurations in separate
|
One popular reason to build several GDB configurations in separate
|
directories is to configure GDB for cross-compiling (where GDB runs on
|
directories is to configure GDB for cross-compiling (where GDB runs on
|
one machine--the host--while debugging programs that run on another
|
one machine--the host--while debugging programs that run on another
|
machine--the target). You specify a cross-debugging target by giving
|
machine--the target). You specify a cross-debugging target by giving
|
the `--target=TARGET' option to `configure'.
|
the `--target=TARGET' option to `configure'.
|
|
|
When you run `make' to build a program or library, you must run it
|
When you run `make' to build a program or library, you must run it
|
in a configured directory--whatever directory you were in when you
|
in a configured directory--whatever directory you were in when you
|
called `configure' (or one of its subdirectories).
|
called `configure' (or one of its subdirectories).
|
|
|
The `Makefile' that `configure' generates in each source directory
|
The `Makefile' that `configure' generates in each source directory
|
also runs recursively. If you type `make' in a source directory such
|
also runs recursively. If you type `make' in a source directory such
|
as `gdb-7.1' (or in a separate configured directory configured with
|
as `gdb-7.1' (or in a separate configured directory configured with
|
`--srcdir=PATH/gdb-7.1'), you will build all the required libraries,
|
`--srcdir=PATH/gdb-7.1'), you will build all the required libraries,
|
and then build GDB.
|
and then build GDB.
|
|
|
When you have multiple hosts or targets configured in separate
|
When you have multiple hosts or targets configured in separate
|
directories, you can run `make' on them in parallel (for example, if
|
directories, you can run `make' on them in parallel (for example, if
|
they are NFS-mounted on each of the hosts); they will not interfere
|
they are NFS-mounted on each of the hosts); they will not interfere
|
with each other.
|
with each other.
|
|
|
|
|
Specifying names for hosts and targets
|
Specifying names for hosts and targets
|
======================================
|
======================================
|
|
|
The specifications used for hosts and targets in the `configure'
|
The specifications used for hosts and targets in the `configure'
|
script are based on a three-part naming scheme, but some short
|
script are based on a three-part naming scheme, but some short
|
predefined aliases are also supported. The full naming scheme encodes
|
predefined aliases are also supported. The full naming scheme encodes
|
three pieces of information in the following pattern:
|
three pieces of information in the following pattern:
|
|
|
ARCHITECTURE-VENDOR-OS
|
ARCHITECTURE-VENDOR-OS
|
|
|
For example, you can use the alias `sun4' as a HOST argument or in a
|
For example, you can use the alias `sun4' as a HOST argument or in a
|
`--target=TARGET' option. The equivalent full name is
|
`--target=TARGET' option. The equivalent full name is
|
`sparc-sun-sunos4'.
|
`sparc-sun-sunos4'.
|
|
|
The `configure' script accompanying GDB does not provide any query
|
The `configure' script accompanying GDB does not provide any query
|
facility to list all supported host and target names or aliases.
|
facility to list all supported host and target names or aliases.
|
`configure' calls the Bourne shell script `config.sub' to map
|
`configure' calls the Bourne shell script `config.sub' to map
|
abbreviations to full names; you can read the script, if you wish, or
|
abbreviations to full names; you can read the script, if you wish, or
|
you can use it to test your guesses on abbreviations--for example:
|
you can use it to test your guesses on abbreviations--for example:
|
|
|
% sh config.sub sun4
|
% sh config.sub sun4
|
sparc-sun-sunos4.1.1
|
sparc-sun-sunos4.1.1
|
% sh config.sub sun3
|
% sh config.sub sun3
|
m68k-sun-sunos4.1.1
|
m68k-sun-sunos4.1.1
|
% sh config.sub decstation
|
% sh config.sub decstation
|
mips-dec-ultrix4.2
|
mips-dec-ultrix4.2
|
% sh config.sub hp300bsd
|
% sh config.sub hp300bsd
|
m68k-hp-bsd
|
m68k-hp-bsd
|
% sh config.sub i386v
|
% sh config.sub i386v
|
i386-pc-sysv
|
i386-pc-sysv
|
% sh config.sub i786v
|
% sh config.sub i786v
|
Invalid configuration `i786v': machine `i786v' not recognized
|
Invalid configuration `i786v': machine `i786v' not recognized
|
|
|
`config.sub' is also distributed in the GDB source directory
|
`config.sub' is also distributed in the GDB source directory
|
(`gdb-7.1', for version 7.1).
|
(`gdb-7.1', for version 7.1).
|
|
|
|
|
`configure' options
|
`configure' options
|
===================
|
===================
|
|
|
Here is a summary of the `configure' options and arguments that are
|
Here is a summary of the `configure' options and arguments that are
|
most often useful for building GDB. `configure' also has several other
|
most often useful for building GDB. `configure' also has several other
|
options not listed here. *note : (configure.info)What Configure Does,
|
options not listed here. *note : (configure.info)What Configure Does,
|
for a full explanation of `configure'.
|
for a full explanation of `configure'.
|
|
|
configure [--help]
|
configure [--help]
|
[--prefix=DIR]
|
[--prefix=DIR]
|
[--srcdir=PATH]
|
[--srcdir=PATH]
|
[--norecursion] [--rm]
|
[--norecursion] [--rm]
|
[--enable-build-warnings]
|
[--enable-build-warnings]
|
[--target=TARGET]
|
[--target=TARGET]
|
[--host=HOST]
|
[--host=HOST]
|
[HOST]
|
[HOST]
|
|
|
You may introduce options with a single `-' rather than `--' if you
|
You may introduce options with a single `-' rather than `--' if you
|
prefer; but you may abbreviate option names if you use `--'.
|
prefer; but you may abbreviate option names if you use `--'.
|
|
|
`--help'
|
`--help'
|
Display a quick summary of how to invoke `configure'.
|
Display a quick summary of how to invoke `configure'.
|
|
|
`-prefix=DIR'
|
`-prefix=DIR'
|
Configure the source to install programs and files under directory
|
Configure the source to install programs and files under directory
|
`DIR'.
|
`DIR'.
|
|
|
`--srcdir=PATH'
|
`--srcdir=PATH'
|
*Warning: using this option requires GNU `make', or another `make'
|
*Warning: using this option requires GNU `make', or another `make'
|
that compatibly implements the `VPATH' feature.*
|
that compatibly implements the `VPATH' feature.*
|
Use this option to make configurations in directories separate
|
Use this option to make configurations in directories separate
|
from the GDB source directories. Among other things, you can use
|
from the GDB source directories. Among other things, you can use
|
this to build (or maintain) several configurations simultaneously,
|
this to build (or maintain) several configurations simultaneously,
|
in separate directories. `configure' writes configuration
|
in separate directories. `configure' writes configuration
|
specific files in the current directory, but arranges for them to
|
specific files in the current directory, but arranges for them to
|
use the source in the directory PATH. `configure' will create
|
use the source in the directory PATH. `configure' will create
|
directories under the working directory in parallel to the source
|
directories under the working directory in parallel to the source
|
directories below PATH.
|
directories below PATH.
|
|
|
`--host=HOST'
|
`--host=HOST'
|
Configure GDB to run on the specified HOST.
|
Configure GDB to run on the specified HOST.
|
|
|
There is no convenient way to generate a list of all available
|
There is no convenient way to generate a list of all available
|
hosts.
|
hosts.
|
|
|
`HOST ...'
|
`HOST ...'
|
Same as `--host=HOST'. If you omit this, GDB will guess; it's
|
Same as `--host=HOST'. If you omit this, GDB will guess; it's
|
quite accurate.
|
quite accurate.
|
|
|
`--norecursion'
|
`--norecursion'
|
Configure only the directory level where `configure' is executed;
|
Configure only the directory level where `configure' is executed;
|
do not propagate configuration to subdirectories.
|
do not propagate configuration to subdirectories.
|
|
|
`--rm'
|
`--rm'
|
Remove the configuration that the other arguments specify.
|
Remove the configuration that the other arguments specify.
|
|
|
`--enable-build-warnings'
|
`--enable-build-warnings'
|
When building the GDB sources, ask the compiler to warn about any
|
When building the GDB sources, ask the compiler to warn about any
|
code which looks even vaguely suspicious. You should only using
|
code which looks even vaguely suspicious. You should only using
|
this feature if you're compiling with GNU CC. It passes the
|
this feature if you're compiling with GNU CC. It passes the
|
following flags:
|
following flags:
|
-Wimplicit
|
-Wimplicit
|
-Wreturn-type
|
-Wreturn-type
|
-Wcomment
|
-Wcomment
|
-Wtrigraphs
|
-Wtrigraphs
|
-Wformat
|
-Wformat
|
-Wparentheses
|
-Wparentheses
|
-Wpointer-arith
|
-Wpointer-arith
|
|
|
`--enable-werror'
|
`--enable-werror'
|
Treat compiler warnings as werrors. Use this only with GCC. It
|
Treat compiler warnings as werrors. Use this only with GCC. It
|
adds the -Werror flag to the compiler, which will fail the
|
adds the -Werror flag to the compiler, which will fail the
|
compilation if the compiler outputs any warning messages.
|
compilation if the compiler outputs any warning messages.
|
|
|
`--target=TARGET'
|
`--target=TARGET'
|
Configure GDB for cross-debugging programs running on the specified
|
Configure GDB for cross-debugging programs running on the specified
|
TARGET. Without this option, GDB is configured to debug programs
|
TARGET. Without this option, GDB is configured to debug programs
|
that run on the same machine (HOST) as GDB itself.
|
that run on the same machine (HOST) as GDB itself.
|
|
|
There is no convenient way to generate a list of all available
|
There is no convenient way to generate a list of all available
|
targets.
|
targets.
|
|
|
`--with-gdb-datadir=PATH'
|
`--with-gdb-datadir=PATH'
|
Set the GDB-specific data directory. GDB will look here for
|
Set the GDB-specific data directory. GDB will look here for
|
certain supporting files or scripts. This defaults to the `gdb'
|
certain supporting files or scripts. This defaults to the `gdb'
|
subdirectory of `datadir' (which can be set using `--datadir').
|
subdirectory of `datadir' (which can be set using `--datadir').
|
|
|
`--with-relocated-sources=DIR'
|
`--with-relocated-sources=DIR'
|
Sets up the default source path substitution rule so that
|
Sets up the default source path substitution rule so that
|
directory names recorded in debug information will be
|
directory names recorded in debug information will be
|
automatically adjusted for any directory under DIR. DIR should
|
automatically adjusted for any directory under DIR. DIR should
|
be a subdirectory of GDB's configured prefix, the one mentioned
|
be a subdirectory of GDB's configured prefix, the one mentioned
|
in the `--prefix' or `--exec-prefix' options to configure. This
|
in the `--prefix' or `--exec-prefix' options to configure. This
|
option is useful if GDB is supposed to be moved to a different
|
option is useful if GDB is supposed to be moved to a different
|
place after it is built.
|
place after it is built.
|
|
|
`--enable-64-bit-bfd'
|
`--enable-64-bit-bfd'
|
Enable 64-bit support in BFD on 32-bit hosts.
|
Enable 64-bit support in BFD on 32-bit hosts.
|
|
|
`--disable-gdbmi'
|
`--disable-gdbmi'
|
Build GDB without the GDB/MI machine interface.
|
Build GDB without the GDB/MI machine interface.
|
|
|
`--enable-tui'
|
`--enable-tui'
|
Build GDB with the text-mode full-screen user interface (TUI).
|
Build GDB with the text-mode full-screen user interface (TUI).
|
Requires a curses library (ncurses and cursesX are also
|
Requires a curses library (ncurses and cursesX are also
|
supported).
|
supported).
|
|
|
`--enable-gdbtk'
|
`--enable-gdbtk'
|
Build GDB with the gdbtk GUI interface. Requires TCL/Tk to be
|
Build GDB with the gdbtk GUI interface. Requires TCL/Tk to be
|
installed.
|
installed.
|
|
|
`--with-libunwind'
|
`--with-libunwind'
|
Use the libunwind library for unwinding function call stack. See
|
Use the libunwind library for unwinding function call stack. See
|
http://www.nongnu.org/libunwind/index.html fro details.
|
http://www.nongnu.org/libunwind/index.html fro details.
|
Supported only on some platforms.
|
Supported only on some platforms.
|
|
|
`--with-curses'
|
`--with-curses'
|
Use the curses library instead of the termcap library, for
|
Use the curses library instead of the termcap library, for
|
text-mode terminal operations.
|
text-mode terminal operations.
|
|
|
`--enable-profiling' Enable profiling of GDB itself. Necessary if you
|
`--enable-profiling' Enable profiling of GDB itself. Necessary if you
|
want to use the "maint set profile" command for profiling GDB.
|
want to use the "maint set profile" command for profiling GDB.
|
Requires the functions `monstartup' and `_mcleanup' to be present
|
Requires the functions `monstartup' and `_mcleanup' to be present
|
in the standard C library used to build GDB, and also requires a
|
in the standard C library used to build GDB, and also requires a
|
compiler that supports the `-pg' option.
|
compiler that supports the `-pg' option.
|
|
|
`--with-system-readline'
|
`--with-system-readline'
|
Use the readline library installed on the host, rather than the
|
Use the readline library installed on the host, rather than the
|
library supplied as part of GDB tarball.
|
library supplied as part of GDB tarball.
|
|
|
`--with-expat'
|
`--with-expat'
|
Build GDB with the libexpat library. (Done by default if
|
Build GDB with the libexpat library. (Done by default if
|
libexpat is installed and found at configure time.) This library
|
libexpat is installed and found at configure time.) This library
|
is used to read XML files supplied with GDB. If it is
|
is used to read XML files supplied with GDB. If it is
|
unavailable, some features, such as remote protocol memory maps,
|
unavailable, some features, such as remote protocol memory maps,
|
target descriptions, and shared library lists, that are based on
|
target descriptions, and shared library lists, that are based on
|
XML files, will not be available in GDB. If your host does not
|
XML files, will not be available in GDB. If your host does not
|
have libexpat installed, you can get the latest version from
|
have libexpat installed, you can get the latest version from
|
http://expat.sourceforge.net.
|
http://expat.sourceforge.net.
|
|
|
`--with-python[=PATH]'
|
`--with-python[=PATH]'
|
Build GDB with Python scripting support. (Done by default if
|
Build GDB with Python scripting support. (Done by default if
|
libpython is present and found at configure time.) Python makes
|
libpython is present and found at configure time.) Python makes
|
GDB scripting much more powerful than the restricted CLI
|
GDB scripting much more powerful than the restricted CLI
|
scripting language. If your host does not have Python installed,
|
scripting language. If your host does not have Python installed,
|
you can find it on http://www.python.org/download/. The oldest
|
you can find it on http://www.python.org/download/. The oldest
|
version of Python supported by GDB is 2.4. The optional argument
|
version of Python supported by GDB is 2.4. The optional argument
|
PATH says where to find the Python headers and libraries; the
|
PATH says where to find the Python headers and libraries; the
|
configure script will look in PATH/include for headers and in
|
configure script will look in PATH/include for headers and in
|
PATH/lib for the libraries.
|
PATH/lib for the libraries.
|
|
|
`--without-included-regex'
|
`--without-included-regex'
|
Don't use the regex library included with GDB (as part of the
|
Don't use the regex library included with GDB (as part of the
|
libiberty library). This is the default on hosts with version 2
|
libiberty library). This is the default on hosts with version 2
|
of the GNU C library.
|
of the GNU C library.
|
|
|
`--with-sysroot=DIR'
|
`--with-sysroot=DIR'
|
Use DIR as the default system root directory for libraries whose
|
Use DIR as the default system root directory for libraries whose
|
file names begin with `/lib' or `/usr/lib'. (The value of DIR
|
file names begin with `/lib' or `/usr/lib'. (The value of DIR
|
can be modified at run time by using the "set sysroot" command.)
|
can be modified at run time by using the "set sysroot" command.)
|
If DIR is under the GDB configured prefix (set with `--prefix' or
|
If DIR is under the GDB configured prefix (set with `--prefix' or
|
`--exec-prefix' options), the default system root will be
|
`--exec-prefix' options), the default system root will be
|
automatically adjusted if and when GDB is moved to a different
|
automatically adjusted if and when GDB is moved to a different
|
location.
|
location.
|
|
|
`--with-system-gdbinit=FILE'
|
`--with-system-gdbinit=FILE'
|
Configure GDB to automatically load a system-wide init file.
|
Configure GDB to automatically load a system-wide init file.
|
FILE should be an absolute file name. If FILE is in a directory
|
FILE should be an absolute file name. If FILE is in a directory
|
under the configured prefix, and GDB is moved to another location
|
under the configured prefix, and GDB is moved to another location
|
after being built, the location of the system-wide init file will
|
after being built, the location of the system-wide init file will
|
be adjusted accordingly.
|
be adjusted accordingly.
|
|
|
`configure' accepts other options, for compatibility with configuring
|
`configure' accepts other options, for compatibility with configuring
|
other GNU tools recursively; but these are the only options that affect
|
other GNU tools recursively; but these are the only options that affect
|
GDB or its supporting libraries.
|
GDB or its supporting libraries.
|
|
|
|
|
Remote debugging
|
Remote debugging
|
=================
|
=================
|
|
|
The files m68k-stub.c, i386-stub.c, and sparc-stub.c are examples
|
The files m68k-stub.c, i386-stub.c, and sparc-stub.c are examples
|
of remote stubs to be used with remote.c. They are designed to run
|
of remote stubs to be used with remote.c. They are designed to run
|
standalone on an m68k, i386, or SPARC cpu and communicate properly
|
standalone on an m68k, i386, or SPARC cpu and communicate properly
|
with the remote.c stub over a serial line.
|
with the remote.c stub over a serial line.
|
|
|
The directory gdb/gdbserver/ contains `gdbserver', a program that
|
The directory gdb/gdbserver/ contains `gdbserver', a program that
|
allows remote debugging for Unix applications. gdbserver is only
|
allows remote debugging for Unix applications. gdbserver is only
|
supported for some native configurations, including Sun 3, Sun 4, and
|
supported for some native configurations, including Sun 3, Sun 4, and
|
Linux.
|
Linux.
|
The file gdb/gdbserver/README includes further notes on gdbserver; in
|
The file gdb/gdbserver/README includes further notes on gdbserver; in
|
particular, it explains how to build gdbserver for cross-debugging
|
particular, it explains how to build gdbserver for cross-debugging
|
(where gdbserver runs on the target machine, which is of a different
|
(where gdbserver runs on the target machine, which is of a different
|
architecture than the host machine running GDB).
|
architecture than the host machine running GDB).
|
|
|
There are a number of remote interfaces for talking to existing ROM
|
There are a number of remote interfaces for talking to existing ROM
|
monitors and other hardware:
|
monitors and other hardware:
|
|
|
remote-mips.c MIPS remote debugging protocol
|
remote-mips.c MIPS remote debugging protocol
|
remote-sds.c PowerPC SDS monitor
|
remote-sds.c PowerPC SDS monitor
|
remote-sim.c Generalized simulator protocol
|
remote-sim.c Generalized simulator protocol
|
|
|
|
|
Reporting Bugs in GDB
|
Reporting Bugs in GDB
|
=====================
|
=====================
|
|
|
There are several ways of reporting bugs in GDB. The prefered
|
There are several ways of reporting bugs in GDB. The prefered
|
method is to use the World Wide Web:
|
method is to use the World Wide Web:
|
|
|
http://www.gnu.org/software/gdb/bugs/
|
http://www.gnu.org/software/gdb/bugs/
|
|
|
As an alternative, the bug report can be submitted, via e-mail, to the
|
As an alternative, the bug report can be submitted, via e-mail, to the
|
address "bug-gdb@gnu.org".
|
address "bug-gdb@gnu.org".
|
|
|
When submitting a bug, please include the GDB version number (e.g.,
|
When submitting a bug, please include the GDB version number (e.g.,
|
gdb-7.1), and how you configured it (e.g., "sun4" or "mach386 host,
|
gdb-7.1), and how you configured it (e.g., "sun4" or "mach386 host,
|
i586-intel-synopsys target"). Since GDB now supports so many
|
i586-intel-synopsys target"). Since GDB now supports so many
|
different configurations, it is important that you be precise about
|
different configurations, it is important that you be precise about
|
this. If at all possible, you should include the actual banner that
|
this. If at all possible, you should include the actual banner that
|
GDB prints when it starts up, or failing that, the actual configure
|
GDB prints when it starts up, or failing that, the actual configure
|
command that you used when configuring GDB.
|
command that you used when configuring GDB.
|
|
|
For more information on how/whether to report bugs, see the
|
For more information on how/whether to report bugs, see the
|
Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo).
|
Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo).
|
|
|
|
|
Graphical interface to GDB -- X Windows, MS Windows
|
Graphical interface to GDB -- X Windows, MS Windows
|
==========================
|
==========================
|
|
|
Several graphical interfaces to GDB are available. You should
|
Several graphical interfaces to GDB are available. You should
|
check:
|
check:
|
|
|
http://www.gnu.org/software/gdb/links/
|
http://www.gnu.org/software/gdb/links/
|
|
|
for an up-to-date list.
|
for an up-to-date list.
|
|
|
Emacs users will very likely enjoy the Grand Unified Debugger mode;
|
Emacs users will very likely enjoy the Grand Unified Debugger mode;
|
try typing `M-x gdb RET'.
|
try typing `M-x gdb RET'.
|
|
|
|
|
Writing Code for GDB
|
Writing Code for GDB
|
=====================
|
=====================
|
|
|
There is a lot of information about writing code for GDB in the
|
There is a lot of information about writing code for GDB in the
|
internals manual, distributed with GDB in gdb/doc/gdbint.texinfo. You
|
internals manual, distributed with GDB in gdb/doc/gdbint.texinfo. You
|
can read it by hand, print it by using TeX and texinfo, or process it
|
can read it by hand, print it by using TeX and texinfo, or process it
|
into an `info' file for use with Emacs' info mode or the standalone
|
into an `info' file for use with Emacs' info mode or the standalone
|
`info' program.
|
`info' program.
|
|
|
If you are pondering writing anything but a short patch, especially
|
If you are pondering writing anything but a short patch, especially
|
take note of the information about copyrights in the node Submitting
|
take note of the information about copyrights in the node Submitting
|
Patches. It can take quite a while to get all the paperwork done, so
|
Patches. It can take quite a while to get all the paperwork done, so
|
we encourage you to start that process as soon as you decide you are
|
we encourage you to start that process as soon as you decide you are
|
planning to work on something, or at least well ahead of when you
|
planning to work on something, or at least well ahead of when you
|
think you will be ready to submit the patches.
|
think you will be ready to submit the patches.
|
|
|
|
|
GDB Testsuite
|
GDB Testsuite
|
=============
|
=============
|
|
|
Included with the GDB distribution is a DejaGNU based testsuite
|
Included with the GDB distribution is a DejaGNU based testsuite
|
that can either be used to test your newly built GDB, or for
|
that can either be used to test your newly built GDB, or for
|
regression testing a GDB with local modifications.
|
regression testing a GDB with local modifications.
|
|
|
Running the testsuite requires the prior installation of DejaGNU,
|
Running the testsuite requires the prior installation of DejaGNU,
|
which is generally available via ftp. The directory
|
which is generally available via ftp. The directory
|
ftp://sources.redhat.com/pub/dejagnu/ will contain a recent snapshot.
|
ftp://sources.redhat.com/pub/dejagnu/ will contain a recent snapshot.
|
Once DejaGNU is installed, you can run the tests in one of the
|
Once DejaGNU is installed, you can run the tests in one of the
|
following ways:
|
following ways:
|
|
|
(1) cd gdb-7.1
|
(1) cd gdb-7.1
|
make check-gdb
|
make check-gdb
|
|
|
or
|
or
|
|
|
(2) cd gdb-7.1/gdb
|
(2) cd gdb-7.1/gdb
|
make check
|
make check
|
|
|
or
|
or
|
|
|
(3) cd gdb-7.1/gdb/testsuite
|
(3) cd gdb-7.1/gdb/testsuite
|
make site.exp (builds the site specific file)
|
make site.exp (builds the site specific file)
|
runtest -tool gdb GDB=../gdb (or GDB= as appropriate)
|
runtest -tool gdb GDB=../gdb (or GDB= as appropriate)
|
|
|
When using a `make'-based method, you can use the Makefile variable
|
When using a `make'-based method, you can use the Makefile variable
|
`RUNTESTFLAGS' to pass flags to `runtest', e.g.:
|
`RUNTESTFLAGS' to pass flags to `runtest', e.g.:
|
|
|
make RUNTESTFLAGS=--directory=gdb.cp check
|
make RUNTESTFLAGS=--directory=gdb.cp check
|
|
|
If you use GNU make, you can use its `-j' option to run the testsuite
|
If you use GNU make, you can use its `-j' option to run the testsuite
|
in parallel. This can greatly reduce the amount of time it takes for
|
in parallel. This can greatly reduce the amount of time it takes for
|
the testsuite to run. In this case, if you set `RUNTESTFLAGS' then,
|
the testsuite to run. In this case, if you set `RUNTESTFLAGS' then,
|
by default, the tests will be run serially even under `-j'. You can
|
by default, the tests will be run serially even under `-j'. You can
|
override this and force a parallel run by setting the `make' variable
|
override this and force a parallel run by setting the `make' variable
|
`FORCE_PARALLEL' to any non-empty value. Note that the parallel `make
|
`FORCE_PARALLEL' to any non-empty value. Note that the parallel `make
|
check' assumes that you want to run the entire testsuite, so it is not
|
check' assumes that you want to run the entire testsuite, so it is not
|
compatible with some dejagnu options, like `--directory'.
|
compatible with some dejagnu options, like `--directory'.
|
|
|
The last method gives you slightly more control in case of problems
|
The last method gives you slightly more control in case of problems
|
with building one or more test executables or if you are using the
|
with building one or more test executables or if you are using the
|
testsuite `standalone', without it being part of the GDB source tree.
|
testsuite `standalone', without it being part of the GDB source tree.
|
|
|
See the DejaGNU documentation for further details.
|
See the DejaGNU documentation for further details.
|
|
|
|
|
(this is for editing this file with GNU emacs)
|
(this is for editing this file with GNU emacs)
|
Local Variables:
|
Local Variables:
|
mode: text
|
mode: text
|
End:
|
End:
|
|
|
