From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Jan Kratochvil" <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Re: Unwinding CFI gcc practice of assumed `same value' regs
Date: Wed, 13 Dec 2006 21:41:00 -0000 [thread overview]
Message-ID: <23342.82.92.89.47.1166046052.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20061213210357.GA27039@nevyn.them.org>
> On Wed, Dec 13, 2006 at 09:46:04PM +0100, Jan Kratochvil wrote:
> > Attaching patch for current gdb CVS to properly terminate on return
> > address 0.
> > The check was already present there but it got applied one backward step
> > later.
> >
> > I hope these three patches are be 100% reliable and also backward
> > compatible.
>
> Please read the previous discussion and patch on this topic:
> http://sourceware.org/ml/gdb-patches/2006-07/msg00392.html
>
> Mark, I don't suppose you find it convincing that the libgcc unwinder
> terminates on PC == 0 too?
It's a perfectly reasonable thing for the libgcc unwinder to do (just
as it is for us in GDB). But in a debugger I want to see that PC == 0
if it is an abnormal backtrace termination.
What really needs to be done is making the DWARF2 unwinder recognize the
condition and return a suitable frame id for that.
Mark
next prev parent reply other threads:[~2006-12-13 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061211190300.GA4372@host0.dyn.jankratochvil.net>
[not found] ` <20061211224022.AD76E1800E7@magilla.sf.frob.com>
[not found] ` <20061212155233.GH29911@devserv.devel.redhat.com>
2006-12-13 20:46 ` Jan Kratochvil
2006-12-13 21:04 ` Daniel Jacobowitz
2006-12-13 21:41 ` Mark Kettenis [this message]
2006-12-13 21:46 ` Daniel Jacobowitz
2006-12-13 21:53 ` Mark Kettenis
2006-12-13 22:11 ` Jan Kratochvil
2006-12-16 23:46 ` Jan Kratochvil
2006-12-17 13:06 ` Mark Kettenis
2006-12-17 18:23 ` Jan Kratochvil
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=23342.82.92.89.47.1166046052.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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