From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15052 invoked by alias); 9 Nov 2005 14:17:26 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 15010 invoked by uid 22791); 9 Nov 2005 14:17:21 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 09 Nov 2005 14:17:21 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EZqlL-0005Sb-It; Wed, 09 Nov 2005 09:17:19 -0500 Date: Wed, 09 Nov 2005 14:17:00 -0000 From: Daniel Jacobowitz To: Olaf Hering Cc: Andreas Schwab , gdb@sourceware.org Subject: Re: trouble with gdb backtraces on ppc with gcc4 Message-ID: <20051109141719.GA20933@nevyn.them.org> Mail-Followup-To: Olaf Hering , Andreas Schwab , gdb@sourceware.org References: <20051109130501.GA16450@suse.de> <20051109140215.GA18309@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051109140215.GA18309@suse.de> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-11/txt/msg00199.txt.bz2 On Wed, Nov 09, 2005 at 03:02:15PM +0100, Olaf Hering wrote: > On Wed, Nov 09, Andreas Schwab wrote: > > > Olaf Hering writes: > > > > > the backtraces in gdb 6.3 and also in gdb-mainline are usually broken in > > > openSuSE. How does gdb generate them? I guess gdb needs to deal with the > > > gcc generated debug info. > > > > When there is one. In your example there isn't. The openSuSE gdb has > > been patched to make use of the DWARF unwind information, which works > > quite well if it is present. FYI, the reason that GDB doesn't is that until fairly recently, GCC generated bogus PPC unwind info (had the wrong register number for LR). Someone ought to see whether it's practical to detect and work around that case. Or maybe we should just require fixed debug info now. -- Daniel Jacobowitz CodeSourcery, LLC