From e6beb4281abec2e792cd149ceb413d439c604626 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Thu, 25 Sep 2003 18:23:56 +0000 Subject: [PATCH] 2003-09-25 Andrew Cagney * NEWS: Mention the new backtrace mechanism, DWARF 2 CFI, hosted file I/O, multi-arch, TLS and NPTL, DWARF 2 Location Expressions, and Java. * PROBLEMS: Mention that mips*-*-*, powerpc*-*-*, sparc*-*-* and arm*-*-* do not use the new frame code. --- gdb/ChangeLog | 8 ++++++++ gdb/NEWS | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++ gdb/PROBLEMS | 20 ++++++++++++++++++ 3 files changed, 85 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 37922af273..1ff07dc298 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,11 @@ +2003-09-25 Andrew Cagney + + * NEWS: Mention the new backtrace mechanism, DWARF 2 CFI, hosted + file I/O, multi-arch, TLS and NPTL, DWARF 2 Location Expressions, + and Java. + * PROBLEMS: Mention that mips*-*-*, powerpc*-*-*, sparc*-*-* and + arm*-*-* do not use the new frame code. + 2003-09-25 David Carlton * c-exp.y: Remove 'register' declarations. diff --git a/gdb/NEWS b/gdb/NEWS index 1a2784abcc..28206bc099 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -16,6 +16,63 @@ SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris *** Changes in GDB 6.0: +* New backtrace mechanism (includes DWARF 2 Call Frame Information). + +DWARF 2's Call Frame Information makes available compiler generated +information that more exactly describes the program's run-time stack. +By using this information, GDB is able to provide more robust stack +backtraces. + +The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets +have been updated to use a new backtrace mechanism which includes +DWARF 2 CFI support. + +* Hosted file I/O. + +GDB's remote protocol has been extended to include support for hosted +file I/O (where the remote target uses GDB's file system). See GDB's +remote protocol documentation for details. + +* All targets using the new architecture framework. + +All of GDB's targets have been updated to use the new internal +architecture framework. The way is now open for future GDB releases +to include cross-architecture native debugging support (i386 on amd64, +ppc32 on ppc64). + +* GNU/Linux's Thread Local Storage (TLS) + +GDB now includes support for for the GNU/Linux implementation of +per-thread variables. + +* GNU/Linux's Native POSIX Thread Library (NPTL) + +GDB's thread code has been updated to work with either the new +GNU/Linux NPTL thread library or the older "LinuxThreads" library. + +* Separate debug info. + +GDB, in conjunction with BINUTILS, now supports a mechanism for +automatically loading debug information from a separate file. Instead +of shipping full debug and non-debug versions of system libraries, +system integrators can now instead ship just the stripped libraries +and optional debug files. + +* DWARF 2 Location Expressions + +DWARF 2 Location Expressions allow the compiler to more completely +describe the location of variables (even in optimized code) to the +debugger. + +GDB now includes preliminary support for location expressions (support +for DW_OP_piece is still missing). + +* Java + +A number of long standing bugs that caused GDB to die while starting a +Java application have been fixed. GDB's Java support is now +considered "useable". + * GNU/Linux support for fork, vfork, and exec. The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode" diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index 7480633303..daecf3250f 100644 --- a/gdb/PROBLEMS +++ b/gdb/PROBLEMS @@ -3,6 +3,26 @@ See also: http://www.gnu.org/software/gdb/bugs/ +mips*-*-* +powerpc*-*-* +sparc*-*-* + +GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated +to use the new frame mechanism. + +People encountering problems with these targets should consult GDB's +web pages and mailing lists (http://www.gnu.org/software/gdb/) to see +if there is an update. + +arm-*-* + +GDB's ARM target, in 6.0, has not been updated to use the new frame +mechanism. + +Fortunatly the ARM target, in the GDB's mainline sources, has been +updated so people encountering problems should consider downloading a +more current GDB (http://www.gnu.org/software/gdb/current). + gdb/1091: Constructor breakpoints ignored gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints -- 2.34.1