From: Daniel Jacobowitz <drow@false.org>
To: Olaf Hering <olh@suse.de>
Cc: Andreas Schwab <schwab@suse.de>, gdb@sourceware.org
Subject: Re: trouble with gdb backtraces on ppc with gcc4
Date: Wed, 09 Nov 2005 14:17:00 -0000 [thread overview]
Message-ID: <20051109141719.GA20933@nevyn.them.org> (raw)
In-Reply-To: <20051109140215.GA18309@suse.de>
On Wed, Nov 09, 2005 at 03:02:15PM +0100, Olaf Hering wrote:
> On Wed, Nov 09, Andreas Schwab wrote:
>
> > Olaf Hering <olh@suse.de> 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
prev parent reply other threads:[~2005-11-09 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 13:05 Olaf Hering
2005-11-09 13:41 ` Andreas Schwab
2005-11-09 14:02 ` Olaf Hering
2005-11-09 14:17 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051109141719.GA20933@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=olh@suse.de \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).