* GDB 6.3 Released
@ 2004-11-12 0:37 Andrew Cagney
0 siblings, 0 replies; only message in thread
From: Andrew Cagney @ 2004-11-12 0:37 UTC (permalink / raw)
GDB 6.3 released!
Release 6.3 of GDB, the GNU Debugger, is now available via anonymous
FTP. GDB is a source-level debugger for C, C++, Java and many other
languages. GDB can target (i.e., debug programs running on) more than
a dozen different processor architectures, and GDB itself can run on
most popular GNU/Linux, Unix and Microsoft Windows variants.
Since the previous release (6.2.1, released 8 weeks ago) we've made
many fixes and enhancements including:
* GDB works with GCC -feliminate-dwarf2-dups
GDB now supports a more compact representation of DWARF-2 debug
information using DW_FORM_ref_addr references. These are produced
by GCC with the option -feliminate-dwarf2-dups and also by some
proprietary compilers. With GCC, you must use GCC 3.3.4 or later
to use -feliminate-dwarf2-dups.
When supported by the host system, GDB will be built with
internationalization (libintl). The task of marking up the sources is
continuing, we're looking forward to our first translation.
Initial support for debugging programs compiled with the GNAT
implementation of the Ada programming language has been integrated
into GDB. In this release, support is limited to expression evaluation.
* New native configurations
* Remote 'p' packet
GDB's remote protocol now includes support for the 'p' packet. This
packet is used to fetch individual registers from a remote inferior.
* END-OF-LIFE registers compatibility module
GDB's internal register infrastructure has been completely rewritten.
The new infrastructure making possible the implementation of key new
features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
GDB 6.3 will be the last release to include the the registers
compatibility module that allowed out-of-date configurations to
continue to work. This change directly impacts the following
powerpc bdm protocol
Unless there is activity to revive these configurations, they will be
made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
* OBSOLETE configurations and files
Configurations that have been declared obsolete in this release have
been commented out. Unless there is activity to revive these
configurations, the next release of GDB will have their sources
You can download GDB from Project GNU's FTP server in the directory:
The vital stats:
Size md5sum Name
17mb 812de9e756d53c749ea5516d9ffa5905 gdb-6.2.tar.gz
13mb 05b928f41fa5b482e49ca2c24762a0ae gdb-6.2.tar.bz2
There is a web page for GDB at:
That page includes information about GDB mailing lists (an
announcement mailing list, developers discussion lists, etc.), details
on how to access GDB's CVS repository, locations for development
snapshots, preformatted documentation, and links to related
information around the net. We will put errata notes and
host-specific tips for this release on-line as any problems come up.
All mailing lists archives are also browsable via the web.
Finally, and most importantly, credit must go to Andreas Schwab,
Ashley Pittman, Baurjan Ismagulov, Corinna Vinschen, Daniel
Jacobowitz, David Anderson, David Carlton, David Lecomber, Elena
Zannoni, Eli Zaretskii, Eric Botcazou, Jason Molenda, Jeff Johnston,
Jerome Guitton, Jim Blandy, Joel Brobecker, Kei Sakamoto, Kevin
Buettner, Maciej W. Rozycki, Manoj Iyer, Mark Kettenis, Martin Hunt,
Michael Chastain, Michael Snyder, Nathan J. Williams, Nathanael
Nerode, Nick Roberts, Orjan Friberg, Paul GIlliam, Paul Hilfinger,
Ramana Radhakrishnan, Randolph Chung, Richard Earnshaw, Robert Millan,
Robert Picco, Salvador E. Tropea, and Ulrich Weigand!
Known problems in GDB 6.3
See also: http://www.gnu.org/software/gdb/bugs/
*** Build problems
build/1411: build fails on hpux 10.20 and hpux 11.00 with CMA threads
GDB does not build on HP/UX 10.20 or HP/UX 11.00 if the CMA
thread package is installed. The compile error is:
../../gdb/hpux-thread.c:222: variable-size type declared outside of any function
This happens only if the CMA thread package is installed.
As a workaround, you can disable support for CMA threads
by editing the file gdb/configure. Find the line:
if test -f /usr/include/dce/cma_config.h ; then
And replace it with:
if false ; then
gdb/1560: Control-C does not always interrupt GDB.
When GDB is busy processing a command which takes a long time to
complete, hitting Control-C does not have the expected effect.
The command execution is not aborted, and the "QUIT" message confirming
the abortion is displayed only after the command has been completed.
*** C++ support
gdb/931: GDB could be more generous when reading types C++ templates on input
When the user types a template, GDB frequently requires the type to be
typed in a certain way (e.g. "const char*" as opposed to "const char *"
or "char const *" or "char const*").
gdb/1512: no canonical way to output names of C++ types
We currently don't have any canonical way to output names of C++ types.
E.g. "const char *" versus "char const *"; more subtleties arise when
dealing with templates.
gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
defined locally to a function include the demangled name of the function
as part of their name. For example, if a function "foobar" contains a
local class definition "Local", gdb will say that the name of the class
type is "foobar__Fi.0:Local".
This applies only to classes where the class type is defined inside a
function, not to variables defined with types that are defined somewhere
outside any function (which most types are).
gdb/1588: names of c++ nested types in casts must be enclosed in quotes
You must type
(gdb) print ('Foo::Bar') x
(gdb) print ('Foo::Bar' *) y
(gdb) print (Foo::Bar) x
(gdb) print (Foo::Bar *) y
gdb/1091: Constructor breakpoints ignored
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
2 or 3 different versions of the object code. These versions have
unique mangled names (they have to, in order for linking to work), but
they have identical source code names, which leads to a great deal of
confusion. Specifically, if you set a breakpoint in a constructor or a
destructor, gdb will put a breakpoint in one of the versions, but your
program may execute the other version. This makes it impossible to set
breakpoints reliably in constructors or destructors.
gcc 3.x generates these multiple object code functions in order to
implement virtual base classes. gcc 2.x generated just one object code
function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
ABI for C++ which requires multiple object code functions.
On GNU/Linux systems that use the old LinuxThreads thread library, a
program rapidly creating and deleting threads can confuse GDB leading
to an internal error.
This problem does not occur on newer systems that use the NPTL
library, and did not occur with GDB 6.1.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-11-12 0:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-11-12 0:37 GDB 6.3 Released Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).