From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8351 invoked by alias); 28 Mar 2004 19:57:35 -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 8340 invoked from network); 28 Mar 2004 19:57:32 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 28 Mar 2004 19:57:32 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B43C72B9C; Sun, 28 Mar 2004 14:57:35 -0500 (EST) Message-ID: <40672E2F.30801@gnu.org> Date: Sun, 28 Mar 2004 19:57:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] PROBLEMS: Stack backtraces References: <40646456.8030601@gnu.org> <1438-Fri26Mar2004202946+0300-eliz@gnu.org> In-Reply-To: <1438-Fri26Mar2004202946+0300-eliz@gnu.org> Content-Type: multipart/mixed; boundary="------------020100090601060500010201" X-SW-Source: 2004-03/txt/msg00706.txt.bz2 This is a multi-part message in MIME format. --------------020100090601060500010201 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 27 I checked this in. Andrew --------------020100090601060500010201 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 2446 2004-03-28 Andrew Cagney * PROBLEMS (Stack backtraces): Rewrite. Remove reference to arm*-*-*. Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.23.2.4 diff -u -r1.23.2.4 PROBLEMS --- PROBLEMS 26 Mar 2004 17:02:52 -0000 1.23.2.4 +++ PROBLEMS 28 Mar 2004 19:45:28 -0000 @@ -70,27 +70,36 @@ *** Stack backtraces +GDB's core code base has been updated to use a new backtrace +mechanism. This mechanism makes it possible to support new features +such DWARF 2 Call Frame Information (which in turn makes possible +backtraces through optimized code). + +Since this code is new, it is known to still have a few problems: + gdb/1505: [regression] gdb prints a bad backtrace for a thread -When backtracing a thread, gdb doesn't stop until it hits garbage. -This is sensitive to the operating system and thread library. +When backtracing a thread, gdb does not stop when it reaches the +outermost frame, instead continuing until it hits garbage. This is +sensitive to the operating system and thread library. +hppa*-*-* mips*-*-* -powerpc*-*-* -sparc*-*-* -GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated -to use the new frame mechanism. +The MIPS and HPPA backtrace code has only very recently been updated +to use GDB's new frame mechanism. At present there are still a few +problems, in particular backtraces through signal handlers do not +work. + +People encountering problems with these architectures should consult +GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/) +to see if there are updates. -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-*-* +powerpc*-*-* -GDB's ARM target, in 6.0, has not been updated to use the new frame -mechanism. +PowerPC architecture support, in 6.1, does not use the new frame code. -Fortunately 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). +Fortunately, PowerPC architecture support, in GDB's mainline sources, +have been updated. People encountering problems should consider +downloading a more current snapshot of GDB +(http://www.gnu.org/software/gdb/current/). --------------020100090601060500010201--