From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3480 invoked by alias); 25 Sep 2003 18:30:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3473 invoked from network); 25 Sep 2003 18:30:06 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 25 Sep 2003 18:30:06 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5D84B2B89 for ; Thu, 25 Sep 2003 14:30:03 -0400 (EDT) Message-ID: <3F73342A.9020906@redhat.com> Date: Thu, 25 Sep 2003 18:30:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: Re: [6.0] PROBLEMS and NEWS References: <3F6CBFA5.7060308@redhat.com> Content-Type: multipart/mixed; boundary="------------090201060902010607060902" X-SW-Source: 2003-09/txt/msg00569.txt.bz2 This is a multi-part message in MIME format. --------------090201060902010607060902 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 38 This is what I've checked in. Andrew --------------090201060902010607060902 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 3833 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. Index: NEWS =================================================================== RCS file: /cvs/src/src/gdb/NEWS,v retrieving revision 1.120 diff -u -r1.120 NEWS --- NEWS 11 Sep 2003 14:00:54 -0000 1.120 +++ NEWS 25 Sep 2003 18:22:53 -0000 @@ -16,6 +16,63 @@ *** 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" Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.18 diff -u -r1.18 PROBLEMS --- PROBLEMS 26 Aug 2003 03:08:32 -0000 1.18 +++ PROBLEMS 25 Sep 2003 18:22:53 -0000 @@ -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 --------------090201060902010607060902--