Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>,
	        "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:53:00 -0000	[thread overview]
Message-ID: <5950.82.92.89.47.1166046772.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20061213214540.GA28965@nevyn.them.org>

>  On Wed, Dec 13, 2006 at 10:40:52PM +0100, Mark Kettenis wrote:
> > 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.
>
>  Sorry, but I'm confused again :-(
>
>  Do you mean making the DWARF2 unwinder decide that ra == 0 is a clean
>  terminator?  That seems like a bad thing to do if you want to ever show
>  PC == 0 as abnormal termination; then it will do so only if the last
>  frame left on the stack didn't have DWARF2 info.  Or do you mean some
>  other change to the unwinder?

No, sorry, it is me who is confused.  I didn't actually look at Jan's patch
and assumed it did the the right thing of marking the return address as
undefined.

Mark


  reply	other threads:[~2006-12-13 21:53 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
2006-12-13 21:46           ` Daniel Jacobowitz
2006-12-13 21:53             ` Mark Kettenis [this message]
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=5950.82.92.89.47.1166046772.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