- Known problems in GDB 5.3
+ Known problems in GDB 6.0
See also: http://www.gnu.org/software/gdb/bugs/
-*-*-freebsd*
----------------
-
-Due to a kernel bug (kern/35175), detaching from an attached process
-will very likely cause the process to be stop or die with a Trace/BPT
-trap.
-
-
-i386-*-freebsd[34]*
--------------------
-
-There is a bug (bin/41671) in FreeBSD's gcc that causes it to emit bad
-debug information when using the stabs format (which is the default).
-As a result GDB tends to place breakpoints on functions before the
-function prologue, and information about function parameters and local
-variables is lost. In earlier versions of GDB the effects were rather
-limited, but starting with GDB 5.3 the influence is much more
-prominent. As a workaround, compile your code with -gdwarf-2.
-
-
-hppa2.0-hp-hpux10.20
---------------------
-
-gdb/487: The top level make files used to build GDB are not compatible
-with HP/UX make. As a workaround, use GNU make.
-
-gdb/486: The HP/UX C compiler defaults to K&R mode but GDB only builds
-with an ISO C compiler. The top level configuration incorrectly sets
-CC to `cc' instead of `cc -Ae'. As a workaround, the correct compiler
-can be specified as part of the configuration vis:
-
- $ 'CC=cc -Ae' ./configure
-
-
-s390*-*-*
----------
-
-gdb/513: GDB does not build on s390 GNU/Linux. The problem should be
-fixed in more recent sources.
-
-
-i386-*-freebsd4.4*
-------------------
-
-gdb/455: GDB doesn't build on a FreeBSD 4.4-STABLE system. The
-problem is still being investigated.
-
-alpha*-*-osf*
--------------
-
-gdb/816: When building GDB with GCC 3.0.1, GDB is unable to load a core
-file properly. It generates several errors and warnings regarding
-unhandled core file section types, incorrect endianness, the failure to
-load the registers. Are also incorrectly reported: The program name, the
-cause of the program death, and the call stack at the moment of the
-death. This problem has been reported on alpha-osf4.0f and alpha-osf5.1a.
-To work-around the problem, add -D__digital__ to the CFLAGS when
-building GDB vis:
-
- $ make CFLAGS='-O2 -D__digital__'
-
-
-i[3456]86-*-linux*
-------------------
-
-gdb/660: gdb does not build with GNU/Linux libc5. The symptom is a
-parse error before `uintptr_t' or an error message about `uintptr_t'.
-Upgrade to glibc 2.1.3 or later, which defines uintptr_t.
-
-gdb/1030: GNU binutils 2.12.1 and earlier versions do not work properly
-with gdb. If you use GNU binutils, upgrade to version 2.13 or later.
-You can check the version of binutils with the command:
-
- $ ld --version
- README for gdb-5.3 release
- Updated 5th September, 2002 by Andrew Cagney
+ README for gdb-6.0 release
+ Updated 23th June, 2003 by Andrew Cagney
This is GDB, the GNU source-level debugger.
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.3 directory. The idea is that a variety of GNU
+underneath the gdb-6.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 release),
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-5.3.tar.gz file, you'll find a directory
-called `gdb-5.3', which contains:
+ When you unpack the gdb-6.0.tar.gz file, you'll find a directory
+called `gdb-6.0', which contains:
COPYING config.sub intl missing opcodes
COPYING.LIB configure libiberty mkinstalldirs readline
You can build GDB right in the source directory:
- cd gdb-5.3
+ cd gdb-6.0
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
mkdir build
cd build
- <full path to your sources>/gdb-5.3/configure
+ <full path to your sources>/gdb-6.0/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-5.3/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.0/gdb/config/djgpp/README for details.)
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'.
- Make sure that your 'configure' line ends in 'gdb-5.3/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.0/configure':
- /berman/migchain/source/gdb-5.3/configure # RIGHT
- /berman/migchain/source/gdb-5.3/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.0/configure # RIGHT
+ /berman/migchain/source/gdb-6.0/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-5.3/gdb/configure', then you are configuring only the gdb
+'gdb-6.0/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
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.3/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.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
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-5.3', in the case of version 5.3), you can make
+source directory (`gdb-6.0', in the case of version 6.0), you can make
the Info file by typing:
cd gdb/doc
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
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-5.3/texinfo'.
+distribution, in the directory `gdb-6.0/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
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-5.3/texinfo' directory.
+`gdb-6.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-5.3/gdb') and then type:
+the main source directory (for example, to `gdb-6.0/gdb') and then type:
make doc/gdb.dvi
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 5.3 distribution is in the `gdb-5.3'
+ For example, the GDB version 6.0 distribution is in the `gdb-6.0'
directory. That directory contains:
-`gdb-5.3/{COPYING,COPYING.LIB}'
+`gdb-6.0/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-5.3/bfd'
+`gdb-6.0/bfd'
source for the Binary File Descriptor library
-`gdb-5.3/config*'
+`gdb-6.0/config*'
script for configuring GDB, along with other support files
-`gdb-5.3/gdb'
+`gdb-6.0/gdb'
the source specific to GDB itself
-`gdb-5.3/include'
+`gdb-6.0/include'
GNU include files
-`gdb-5.3/libiberty'
+`gdb-6.0/libiberty'
source for the `-liberty' free software library
-`gdb-5.3/mmalloc'
+`gdb-6.0/mmalloc'
source for the GNU memory-mapped malloc package
-`gdb-5.3/opcodes'
+`gdb-6.0/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-5.3/readline'
+`gdb-6.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-5.3/sim'
+`gdb-6.0/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-5.3/intl'
+`gdb-6.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.3/texinfo'
+`gdb-6.0/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-5.3/etc'
+`gdb-6.0/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
-`gdb-5.3/utils'
+`gdb-6.0/utils'
A grab bag of random utilities.
Note: the following instructions are for building GDB on Unix or
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-5.3' directory.
+is the `gdb-6.0' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-5.3
+ cd gdb-6.0
./configure
make
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-5.3'
-source directory for version 5.3, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.0'
+source directory for version 6.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 5.3, type the following to configure only
+ For example, with version 6.0, type the following to configure only
the `bfd' subdirectory:
- cd gdb-5.3/bfd
+ cd gdb-6.0/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 5.3, you can build GDB in a separate
+ For example, with version 6.0, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-5.3
+ cd gdb-6.0
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-5.3/configure
+ ../gdb-6.0/configure
make
When `configure' builds a configuration using a remote source
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-5.3' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-5.3'), you will build all the required libraries,
+as `gdb-6.0' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.0'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-5.3', for version 5.3).
+(`gdb-6.0', for version 6.0).
`configure' options
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-5.3), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.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
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-5.3
+ (1) cd gdb-6.0
make check-gdb
or
- (2) cd gdb-5.3/gdb
+ (2) cd gdb-6.0/gdb
make check
or
- (3) cd gdb-5.3/gdb/testsuite
+ (3) cd gdb-6.0/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
projects / binutils-gdb.git / commitdiff