- README for gdb-4.7 release
- Stu Grossman & John Gilmore 23 October 1992
+ README for gdb-5.0 release
+ Updated 11 May 2000 by Andrew Cagney
-This is GDB, the GNU source-level debugger, presently running under un*x.
+This is GDB, the GNU source-level debugger.
A summary of new features is in the file `NEWS'.
+See the GDB home page at http://sourceware.cygnus.com/gdb/ for up to
+date release information, mailing list links and archives, etc.
+
Unpacking and Installation -- quick overview
==========================
-In this release, the GDB debugger sources, the generic GNU include
-files, the BFD ("binary file description") library, the readline library,
-and other libraries all have directories of their own underneath
-the gdb-4.7 directory. The idea is that a variety of GNU tools can
-share a common copy of these things. Configuration scripts and
-makefiles exist to cruise up and down this directory tree and
-automatically build all the pieces in the right order.
-
-When you unpack the gdb-4.7.tar.Z file, you'll get a directory called
-`gdb-4.7', which contains:
-
- COPYING.LIB config/ configure.texi mmalloc/
- Makefile.in config.sub* gdb/ move-if-change*
- README configure* glob/ opcodes/
- bfd/ configure.in include/ readline/
- cfg-paper.texi configure.man libiberty/ texinfo/
-
-To build GDB, you can just do:
-
- cd gdb-4.7
- ./configure HOSTTYPE (e.g. sun4, decstation)
+ In this release, the GDB debugger sources, the generic GNU include
+files, the BFD ("binary file description") library, the readline
+library, and other libraries all have directories of their own
+underneath the gdb-5.0 directory. The idea is that a variety of GNU
+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
+a release other than the gdb release (such as a binutils or gas
+release), especially if the releases are more than a few weeks apart.
+Configuration scripts and makefiles exist to cruise up and down this
+directory tree and automatically build all the pieces in the right
+order.
+
+ When you unpack the gdb-5.0.tar.gz file, you'll find a directory
+called `gdb-5.0', which contains:
+
+ COPYING config.if install-sh mmalloc readline
+ COPYING.LIB config.sub intl move-if-change sim
+ Makefile.in configure libiberty mpw-README symlink-tree
+ README configure.in ltconfig mpw-build.in texinfo
+ bfd djunpack.bat ltmain.sh mpw-config.in utils
+ config etc md5.sum mpw-configure ylwrap
+ config-ml.in gdb missing mpw-install
+ config.guess include mkinstalldirs opcodes
+
+You can build GDB right in the source directory:
+
+ cd gdb-5.0
+ ./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
-This will configure and build all the libraries as well as GDB.
-If you get compiler warnings during this stage, see the `Reporting Bugs'
-section below; there are a few known problems.
+However, we recommend that an empty directory be used instead.
+This way you do not clutter your source tree with binary files
+and will be able to create different builds with different
+configuration options.
+
+You can build GDB in any empty build directory:
-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. See below.
+
+ mkdir build
+ cd build
+ <full path to your sources>/gdb-5.0/configure
+ make
+(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
+different; see the file gdb-5.0/gdb/config/djgpp/README for details.)
-More Documentation
-******************
+ This will configure and build all the libraries as well as GDB. If
+`configure' can't determine your system type, specify one as its
+argument, e.g., `./configure sun4' or `./configure decstation'.
- The GDB 4 release includes an already-formatted reference card, ready
-for printing with PostScript or GhostScript, in the `gdb' subdirectory
-of the main source directory--in `gdb-4.7/gdb/refcard.ps' of the
-version 4.7 release. If you can use PostScript or GhostScript with your
-printer, you can print the reference card immediately with `refcard.ps'.
+ If you get compiler errors during this stage, see the `Reporting
+Bugs' section below; there are a few known problems.
- The release also includes the source for the reference card. You
-can format it, using TeX, by typing:
+ 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 the GNU CC compiler. It is available via anonymous FTP from
+the directory `ftp://ftp.gnu.org/pub/gnu/gcc'.
- make refcard.dvi
+ 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.
+See below.
- The GDB reference card is designed to print in landscape mode on US
-"letter" size paper; that is, on a sheet 11 inches wide by 8.5 inches
-high. You will need to specify this form of printing as an option to
-your DVI output program.
+
+More Documentation
+******************
All the documentation for GDB comes as part of the machine-readable
-distribution. The documentation is written in Texinfo format, which 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 Info
-formatting commands to create the on-line version of the documentation
-and TeX (or `texi2roff') to typeset the printed version.
-
- GDB includes an already formatted copy of the on-line Info version of
-this manual in the `gdb' subdirectory. The main Info file is
-`gdb-VERSION-NUMBER/gdb/gdb.info', and it refers to subordinate files
+distribution. The documentation is written in Texinfo format, which
+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
+Info formatting commands to create the on-line version of the
+documentation and TeX (or `texi2roff') to typeset the printed 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
+`gdb-5.0/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
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
distribution.
If you want to format these Info files yourself, you need one of the
-Info formatting programs, such as `texinfo-format-buffer' or `makeinfo'.
+Info formatting programs, such as `texinfo-format-buffer' or
+`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-4.7', in the case of version 4.7), you can make
+source directory (`gdb-5.0', in the case of version 5.0), you can make
the Info file by typing:
- cd gdb
- make gdb.info
+ cd gdb/doc
+ make info
If you want to typeset and print copies of this manual, you need
-TeX, a printing program such as `lpr', and `texinfo.tex', the Texinfo
-definitions file.
+TeX, a program to print its DVI output files, and `texinfo.tex', the
+Texinfo definitions file. This file is included in the GDB
+distribution, in the directory `gdb-5.0/texinfo'.
- TeX is 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,
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
-use depends on your system; `lpr -d' is common; another is `dvips'.
-The DVI print command may require a file name without any extension or
-a `.dvi' extension.
+use depends on your system; `lpr -d' is common; another (for PostScript
+devices) is `dvips'. The DVI print command may require a file name
+without any extension or a `.dvi' extension.
TeX also requires a macro definitions file called `texinfo.tex'.
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.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-VERSION-NUMBER/texinfo' directory.
+`gdb-5.0/texinfo' directory.
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
-the main source directory (for example, to `gdb-4.7/gdb') and then type:
+the main source directory (for example, to `gdb-5.0/gdb') and then type:
make gdb.dvi
Installing GDB
-***************
+**************
GDB comes with a `configure' script that automates the process of
preparing GDB for installation; you can then use `make' to build the
-program.
+`gdb' program.
The GDB distribution includes all the source code you need for GDB in
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 4.7 distribution is in the `gdb-4.7'
+ For example, the GDB version 5.0 distribution is in the `gdb-5.0'
directory. That directory contains:
-`gdb-4.7/configure (and supporting files)'
- script for configuring GDB and all its supporting libraries.
+`gdb-5.0/{COPYING,COPYING.LIB}'
+ Standard GNU license files. Please read them.
-`gdb-4.7/gdb'
- the source specific to GDB itself
-
-`gdb-4.7/bfd'
+`gdb-5.0/bfd'
source for the Binary File Descriptor library
-`gdb-4.7/include'
+`gdb-5.0/config*'
+ script for configuring GDB, along with other support files
+
+`gdb-5.0/gdb'
+ the source specific to GDB itself
+
+`gdb-5.0/include'
GNU include files
-`gdb-4.7/libiberty'
+`gdb-5.0/libiberty'
source for the `-liberty' free software library
-`gdb-4.7/opcodes'
+`gdb-5.0/mmalloc'
+ source for the GNU memory-mapped malloc package
+
+`gdb-5.0/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-4.7/readline'
+`gdb-5.0/readline'
source for the GNU command-line interface
+ NOTE: The readline library is compiled for use by GDB, but will
+ not be installed on your system when "make install" is issued.
-`gdb-4.7/glob'
- source for the GNU filename pattern-matching subroutine
+`gdb-5.0/sim'
+ source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-4.7/mmalloc'
- source for the GNU memory-mapped malloc package
+`gdb-5.0/intl'
+ source for the GNU gettext library, for internationalization.
+ This is slightly modified from the standalone gettext
+ distribution you can get from GNU.
+
+`gdb-5.0/texinfo'
+ The `texinfo.tex' file, which you need in order to make a printed
+ manual using TeX.
+
+`gdb-5.0/etc'
+ Coding standards, useful files for editing GDB, and other
+ miscellanea.
+
+`gdb-5.0/utils'
+ A grab bag of random utilities.
+
+ Note: the following instructions are for building GDB on Unix or
+Unix-like systems. Instructions for building with DJGPP for
+MS-DOS/MS-Windows are in the file gdb/config/djgpp/README.
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-4.7' directory.
+is the `gdb-5.0' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
-not already in it; then run `configure'. Pass the identifier for the
-platform on which GDB will run as an argument.
+not already in it; then run `configure'.
For example:
- cd gdb-4.7
- ./configure HOST
+ cd gdb-5.0
+ ./configure
make
-where HOST is an identifier such as `sun4' or `decstation', that
-identifies the platform where GDB will run.
-
- Running `configure HOST' followed by `make' builds the `bfd',
-`readline', `mmalloc', and `libiberty' libraries, then `gdb' itself.
+ Running `configure' followed by `make' builds the `bfd',
+`readline', `mmalloc', and `libiberty' libraries, then `gdb' itself.
The configured source files, and the binaries, are left in the
corresponding source directories.
does not recognize this automatically when you run a different shell,
you may need to run `sh' on it explicitly:
- sh configure HOST
+ sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-4.7'
-source directory for version 4.7, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-5.0'
+source directory for version 5.0, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 4.7, type the following to configure only
+ For example, with version 5.0, type the following to configure only
the `bfd' subdirectory:
- cd gdb-4.7/bfd
- ../configure HOST
+ cd gdb-5.0/bfd
+ ../configure
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'
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,
-you'll 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
generate each configuration in a separate subdirectory, rather than in
the source directory. If your `make' program handles the `VPATH'
-feature (GNU `make' does), running `make' in each of these directories
-then builds the `gdb' program specified there.
+feature correctly (GNU `make' and SunOS 'make' are two that should),
+running `make' in each of these directories builds the `gdb' program
+specified there.
To build `gdb' in a separate directory, run `configure' with the
-`--srcdir' option to specify where to find the source. (You'll also
-need to specify a path to find `configure' itself from your working
+`--srcdir' option to specify where to find the source. (You also need
+to specify a path to find `configure' itself from your working
directory. If the path to `configure' would be the same as the
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 4.7, you can build GDB in a separate
+ For example, with version 5.0, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-4.7
+ cd gdb-5.0
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-4.7/configure sun4
+ ../gdb-5.0/configure
make
When `configure' builds a configuration using a remote source
in a configured directory--whatever directory you were in when you
called `configure' (or one of its subdirectories).
- The `Makefile' generated by `configure' for each source directory
+ The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-4.7' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-4.7'), you will build all the required libraries,
-then build GDB.
+as `gdb-5.0' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-5.0'), you will build all the required libraries,
+and then build GDB.
When you have multiple hosts or targets configured in separate
directories, you can run `make' on them in parallel (for example, if
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'
script are based on a three-part naming scheme, but some short
ARCHITECTURE-VENDOR-OS
For example, you can use the alias `sun4' as a HOST argument or in a
-`--target=TARGET' option, but the equivalent full name is
+`--target=TARGET' option. The equivalent full name is
`sparc-sun-sunos4'.
The `configure' script accompanying GDB does not provide any query
you can use it to test your guesses on abbreviations--for example:
% sh config.sub sun4
- sparc-sun-sunos411
+ sparc-sun-sunos4.1.1
% sh config.sub sun3
- m68k-sun-sunos411
+ m68k-sun-sunos4.1.1
% sh config.sub decstation
- mips-dec-ultrix42
+ mips-dec-ultrix4.2
% sh config.sub hp300bsd
m68k-hp-bsd
% sh config.sub i386v
- i386-unknown-sysv
+ i386-pc-sysv
% sh config.sub i786v
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-4.7', for version 4.7).
+(`gdb-5.0', for version 5.0).
-`configure' Options
-====================
+`configure' options
+===================
Here is a summary of the `configure' options and arguments that are
most often useful for building GDB. `configure' also has several other
[--prefix=DIR]
[--srcdir=PATH]
[--norecursion] [--rm]
- [--target=TARGET] HOST
+ [--enable-build-warnings]
+ [--target=TARGET]
+ [--host=HOST]
+ [HOST]
You may introduce options with a single `-' rather than `--' if you
prefer; but you may abbreviate option names if you use `--'.
`--srcdir=PATH'
*Warning: using this option requires GNU `make', or another `make'
- that implements the `VPATH' feature.*
+ that compatibly implements the `VPATH' feature.*
Use this option to make configurations in directories separate
from the GDB source directories. Among other things, you can use
this to build (or maintain) several configurations simultaneously,
`--rm'
Remove the configuration that the other arguments specify.
+`--enable-build-warnings'
+ When building the GDB sources, ask the compiler to warn about any
+ code which looks even vaguely suspicious. You should only using
+ this feature if you're compiling with GNU CC. It passes the
+ following flags:
+ -Wimplicit
+ -Wreturn-type
+ -Wcomment
+ -Wtrigraphs
+ -Wformat
+ -Wparentheses
+ -Wpointer-arith
+
`--target=TARGET'
Configure GDB for cross-debugging programs running on the specified
TARGET. Without this option, GDB is configured to debug programs
There is no convenient way to generate a list of all available
targets.
-`HOST ...'
+`--host=HOST'
Configure GDB to run on the specified HOST.
There is no convenient way to generate a list of all available
hosts.
+`HOST ...'
+ Same as `--host=HOST'. If you omit this, GDB will guess; it's
+ quite accurate.
+
`configure' accepts other options, for compatibility with configuring
other GNU tools recursively; but these are the only options that affect
GDB or its supporting libraries.
-
Languages other than C
=======================
-GDB provides some support for debugging C++ progams. Partial Modula-2
-support is now in GDB. GDB should work with FORTRAN programs. (If you
-have problems, please send a bug report; you may have to refer to some
-FORTRAN variables with a trailing underscore). I am not aware of
-anyone who is working on getting gdb to use the syntax of any other
-language. Pascal programs which use sets, subranges, file variables,
-or nested functions will not currently work.
+See the GDB manual (gdb/doc/gdb.texinfo) for information on this.
Kernel debugging
=================
-I have't done this myself so I can't really offer any advice.
-Remote debugging over serial lines works fine, but the kernel debugging
-code in here has not been tested in years. Van Jacobson has
+ Remote debugging over serial lines works fine, but the kernel
+debugging code in here has not been tested in years. Van Jacobson has
better kernel debugging, but the UC lawyers won't let FSF have it.
Remote debugging
=================
-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
-standalone on a 68k, 386, or SPARC cpu and communicate properly with
-the remote.c stub over a serial line.
+ 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
+standalone on an m68k, i386, or SPARC cpu and communicate properly
+with the remote.c stub over a serial line.
-The file rem-multi.shar contains a general stub that can probably
-run on various different flavors of unix to allow debugging over a
-serial line from one machine to another.
+ The directory gdb/gdbserver/ contains `gdbserver', a program that
+allows remote debugging for Unix applications. gdbserver is only
+supported for some native configurations, including Sun 3, Sun 4, and
+Linux.
-Some working remote interfaces for talking to existing ROM monitors
-are:
+ There are a number of remote interfaces for talking to existing ROM
+monitors and other hardware:
+
+ remote-adapt.c AMD 29000 "Adapt"
+ remote-array.c Array Tech RAID controller
+ remote-bug.c Motorola BUG monitor
+ remote-e7000.c Hitachi E7000 ICE
remote-eb.c AMD 29000 "EBMON"
+ remote-es.c Ericsson 1800 monitor
+ remote-est.c EST emulator
remote-hms.c Hitachi Micro Systems H8/300 monitor
- remote-nindy.c Intel 960 "Nindy"
- remote-adapt.c AMD 29000 "Adapt"
+ remote-mips.c MIPS remote debugging protocol
remote-mm.c AMD 29000 "minimon"
-
-Remote-vx.c and the vx-share subdirectory contain a remote interface for the
-VxWorks realtime kernel, which communicates over TCP using the Sun
-RPC library. This would be a useful starting point for other remote-
-via-ethernet back ends.
+ remote-nindy.c Intel 960 "Nindy"
+ remote-nrom.c NetROM ROM emulator
+ remote-os9k.c PC running OS/9000
+ remote-rdi.c ARM with Angel monitor
+ remote-rdp.c ARM with Demon monitor
+ remote-sds.c PowerPC SDS monitor
+ remote-sim.c Generalized simulator protocol
+ remote-st.c Tandem ST-2000 monitor
+ remote-udi.c AMD 29000 using the AMD "Universal Debug Interface"
+ remote-vx.c VxWorks realtime kernel
+
+ Remote-vx.c and the vx-share subdirectory contain a remote
+interface for the VxWorks realtime kernel, which communicates over TCP
+using the Sun RPC library. This would be a useful starting point for
+other remote- via-ethernet back ends.
+
+ Remote-udi.c and the 29k-share subdirectory contain a remote
+interface for AMD 29000 programs, which uses the AMD "Universal Debug
+Interface". This allows GDB to talk to software simulators,
+emulators, and/or bare hardware boards, via network or serial
+interfaces. Note that GDB only provides an interface that speaks UDI,
+not a complete solution. You will need something on the other end
+that also speaks UDI.
Reporting Bugs
===============
-The correct address for reporting bugs found in gdb is
-"bug-gdb@prep.ai.mit.edu". Please email all bugs to that address.
-Please include the GDB version number (e.g. gdb-4.7), and how
-you configured it (e.g. "sun4" or "mach386 host, i586-intel-synopsys
-target").
-
-A known bug:
-
- * If you run with a watchpoint enabled, breakpoints will become
- erratic and might not stop the program. Disabling or deleting the
- watchpoint will fix the problem.
-
-GDB can produce warnings about symbols that it does not understand. By
-default, these warnings are disabled. You can enable them by executing
-`set complaint 10' (which you can put in your ~/.gdbinit if you like).
-I recommend doing this if you are working on a compiler, assembler,
-linker, or gdb, since it will point out problems that you may be able
-to fix. Warnings produced during symbol reading indicate some mismatch
-between the object file and GDB's symbol reading code. In many cases,
-it's a mismatch between the specs for the object file format, and what
-the compiler actually outputs or the debugger actually understands.
-
-If you port gdb to a new machine, please send the required changes to
-bug-gdb@prep.ai.mit.edu. There's lots of information about doing your
-own port in the file gdb-4.7/gdb/doc/gdbint.texinfo, which you can
-print out, or read with `info' (see the Makefile.in there). If your
-changes are more than a few lines, obtain and send in a copyright
-assignment from gnu@prep.ai.mit.edu, as described in the section
-`Writing Code for GDB' below.
-
-
-X Windows versus GDB
-=====================
+ The correct address for reporting bugs found in gdb is
+"bug-gdb@gnu.org". Please email all bugs, and all requests for help
+with GDB, to that address. Please include the GDB version number
+(e.g., gdb-5.0), and how you configured it (e.g., "sun4" or "mach386
+host, i586-intel-synopsys target"). Since GDB now supports so many
+different configurations, it is important that you be precise about
+this. If at all possible, you should include the actual banner that
+GDB prints when it starts up, or failing that, the actual configure
+command that you used when configuring GDB.
+
+ For more information on how/whether to report bugs, see the GDB
+Bugs section of the GDB manual (gdb/doc/gdb.texinfo) or the
+gdb/CONTRIBUTE file.
+
+Known bugs:
+
+ * Under Ultrix 4.2 (DECstation-3100) or Alphas under OSF/1, we have
+ seen problems with backtraces after interrupting the inferior out
+ of a read(). The problem is caused by ptrace() returning an
+ incorrect value for the frame pointer register (register 15 or
+ 30). As far as we can tell, this is a kernel problem. Any help
+ with this would be greatly appreciated.
+
+ * Under Ultrix 4.4 (DECstation-3100), setting the TERMCAP environment
+ variable to a string without a trailing ':' can cause GDB to dump
+ core upon startup. Although the core file makes it look as though
+ GDB code failed, the crash actually occurs within a call to the
+ termcap library function tgetent(). The problem can be solved by
+ using the GNU Termcap library.
+
+ Alphas running OSF/1 (versions 1.0 through 2.1) have the same buggy
+ termcap code, but GDB behaves strangely rather than crashing.
+
+ * On DECstations there are warnings about shift counts out of range in
+ various BFD modules. None of them is a cause for alarm, they are actually
+ a result of bugs in the DECstation compiler.
+
+ * Notes for the DEC Alpha using OSF/1:
+ The debugging output of native cc has two known problems; we view these
+ as compiler bugs.
+ The linker miscompacts symbol tables, which causes gdb to confuse the
+ type of variables or results in `struct <illegal>' type outputs.
+ dbx has the same problems with those executables. A workaround is to
+ specify -Wl,-b when linking, but that will increase the executable size
+ considerably.
+ If a structure has incomplete type in one file (e.g., "struct foo *"
+ without a definition for "struct foo"), gdb will be unable to find the
+ structure definition from another file.
+ It has been reported that the Ultrix 4.3A compiler on decstations has the
+ same problems.
+
+ * Notes for Solaris 2.x, using the SPARCworks cc compiler:
+ You have to compile your program with the -xs option of the SPARCworks
+ compiler to be able to debug your program with gdb.
+ Under Solaris 2.3 you also need patch 101409-03 (Jumbo linker patch).
+ Under Solaris 2.2, if you have patch 101052 installed, make sure
+ that it is at least at revision 101052-06.
+
+ * Under Irix 5 for SGIs, you must have installed the `compiler_dev.hdr'
+ subsystem that is on the IDO CD, otherwise you will get complaints
+ that certain files such as `/usr/include/syms.h' cannot be found.
+
+ * Under Irix 6 you must build with GCC. The vendor compiler reports
+ as errors certain assignments that GCC considers to be warnings.
+
+ GDB can produce warnings about symbols that it does not understand.
+By default, these warnings are disabled. You can enable them by
+executing `set complaint 10' (which you can put in your ~/.gdbinit if
+you like). I recommend doing this if you are working on a compiler,
+assembler, linker, or GDB, since it will point out problems that you
+may be able to fix. Warnings produced during symbol reading indicate
+some mismatch between the object file and GDB's symbol reading code.
+In many cases, it's a mismatch between the specs for the object file
+format, and what the compiler actually outputs or the debugger
+actually understands.
+
+
+Graphical interface to GDB -- X Windows, MS Windows
+==========================
+
+ Several graphical interfaces to GDB are available. You should
+check:
-xgdb is obsolete. We are not doing any development or support of it.
+ http://sourceware.cygnus.com/gdb/#gui
-There is an "xxgdb", which shows more promise, which was posted to
-comp.sources.x.
+for an up-to-date list.
-For those intersted in auto display of source and the availability of
-an editor while debugging I suggest trying gdb-mode in gnu-emacs
-(Try typing M-x gdb RETURN). Comments on this mode are welcome.
+ Emacs users will very likely enjoy the Grand Unified Debugger mode;
+try typing `M-x gdb RET'. Those interested in experimenting with a
+new kind of gdb-mode should load gdb/gdba.el into GNU Emacs 19.25 or
+later. Comments on this mode are also welcome.
Writing Code for GDB
=====================
-Documentation about GDB's internals is in the subdirectory doc, as
-`gdbint.texinfo'. In particular, there is a `cookbook' there on how
-to port GDB to a new machine. You 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 `info' program.
-
-We appreciate having users contribute code that is of general use, but
-for it to be included in future GDB releases it must be cleanly
-written. We do not want to include changes that will needlessly make
-future maintainance difficult. It is not much harder to do things
-right, and in the long term it is worth it to the GNU project, and
-probably to you individually as well.
-
-If you make substantial changes, you'll have to file a copyright
-assignment with the Free Software Foundation before we can produce a
-release that includes your changes. Send mail requesting the copyright
-assignment to gnu@prep.ai.mit.edu. Do this early, like before the
-changes actually work, or even before you start them, because a manager
-or lawyer on your end will probably make this a slow process.
-
-Please code according to the GNU coding standards. If you do not have
-a copy, you can request one by sending mail to gnu@prep.ai.mit.edu.
-
-Please try to avoid making machine-specific changes to
-machine-independent files. If this is unavoidable, put a hook in the
-machine-independent file which calls a (possibly) machine-dependent
-macro (for example, the IGNORE_SYMBOL macro can be used for any
-symbols which need to be ignored on a specific machine. Calling
-IGNORE_SYMBOL in dbxread.c is a lot cleaner than a maze of #if
-defined's). The machine-independent code should do whatever "most"
-machines want if the macro is not defined in param.h. Using #if
-defined can sometimes be OK (e.g. SET_STACK_LIMIT_HUGE) but should be
-conditionalized on a specific feature of an operating system (set in
-tm.h or xm.h) rather than something like #if defined(vax) or #if
-defined(SYSV). If you use an #ifdef on some symbol that is defined
-in a header file (e.g. #ifdef TIOCSETP), *please* make sure that you
-have #include'd the relevant header file in that module!
-
-There is a list of all known `feature-test macros' in gdbint.texinfo.
-Each such macro should be defined (or left undefined) in a host-dependent,
-target-dependent, or native-dependent include file. Not all of the
-macros are cleanly separated this way, yet. As you make changes, move
-the code toward cleanliness.
-
-It is better to replace entire routines which may be system-specific,
-rather than put in a whole bunch of hooks which are probably not going
-to be helpful for any purpose other than your changes. For example,
-if you want to modify dbxread.c to deal with DBX debugging symbols
-which are in COFF files rather than BSD a.out files, do something
-along the lines of a macro GET_NEXT_SYMBOL, which could have
-different definitions for COFF and a.out, rather than trying to put
-the necessary changes throughout all the code in dbxread.c that
-currently assumes BSD format.
-
-When generalizing GDB along a particular interface, please use an
-attribute-struct rather than inserting tests or switch statements
-everywhere. For example, GDB has been generalized to handle multiple
-kinds of remote interfaces -- not by #ifdef's everywhere, but by
-defining the "target_ops" structure and having a current target (as
-well as a stack of targets below it, for memory references). Whenever
-something needs to be done that depends on which remote interface we
-are using, a flag in the current target_ops structure is tested (e.g.
-`target_has_stack'), or a function is called through a pointer in the
-current target_ops structure. In this way, when a new remote interface
-is added, only one module needs to be touched -- the one that actually
-implements the new remote interface. Other examples of
-attribute-structs are BFD access to multiple kinds of object file
-formats, or GDB's access to multiple source languages.
-
-Please avoid duplicating code. For example, in GDB 3.x all the stuff
-in infptrace.c was duplicated in *-dep.c, and so changing something
-was very painful. In GDB 4.x, these have all been consolidated
-into infptrace.c. infptrace.c can deal with variations between
-systems the same way any system-independent file would (hooks, #if
-defined, etc.), and machines which are radically different don't need
-to use infptrace.c at all. The same was true of core_file_command
-and exec_file_command.
-
-
-Debugging gdb with itself
-==========================
+ There is a lot of information about writing code for GDB in the
+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
+into an `info' file for use with Emacs' info mode or the standalone
+`info' program.
+
+ If you are pondering writing anything but a short patch, especially
+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
+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
+think you will be ready to submit the patches.
+
+
+GDB Testsuite
+=============
+
+ Included with the GDB distribution is a DejaGNU based testsuite
+that can either be used to test your newly built GDB, or for
+regression testing a GDB with local modifications.
+
+ Running the testsuite requires the prior installation of DejaGNU,
+which is generally available via ftp. The directory
+ftp://sourceware.cygnus.com/pub/dejagnu/ will contain a recent
+snapshot. Once DejaGNU is installed, you can run the tests in one of
+the following ways:
+
+ (1) cd gdb-5.0
+ make check-gdb
+
+or
+
+ (2) cd gdb-5.0/gdb
+ make check
-If gdb is limping on your machine, this is the preferred way to get it
-fully functional. Be warned that in some ancient Unix systems, like
-Ultrix 4.0, a program can't be running in one process while it is being
-debugged in another. Rather than doing "./gdb ./gdb", which works on
-Suns and such, you can copy gdb to gdb2 and then do "./gdb ./gdb2".
+or
-When you run gdb in the gdb source directory, it will read a ".gdbinit"
-file that sets up some simple things to make debugging gdb easier. The
-"info" command, when executed without a subcommand in a gdb being
-debugged by gdb, will pop you back up to the top level gdb. See
-.gdbinit for details.
+ (3) cd gdb-5.0/gdb/testsuite
+ make site.exp (builds the site specific file)
+ runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
-I strongly recommend printing out the reference card and using it.
-Send reference-card suggestions to bug-gdb@prep.ai.mit.edu, just like bugs.
+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
+testsuite `standalone', without it being part of the GDB source tree.
-If you use emacs, you will probably want to do a "make TAGS" after you
-configure your distribution; this will put the machine dependent
-routines for your local machine where they will be accessed first by a
-M-period.
+See the DejaGNU documentation for further details.
-Also, make sure that you've either compiled gdb with your local cc, or
-have run `fixincludes' if you are compiling with gcc.
\f
(this is for editing this file with GNU emacs)
Local Variables: