Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
	 msnyder@vmware.com,   gdb-patches@sourceware.org,
	 teawater@gmail.com
Subject: Re: [RFA] epilogue unwinder for i386 (reverse 1/2)
Date: Sun, 05 Jul 2009 20:46:00 -0000	[thread overview]
Message-ID: <4A51105D.5010400@vmware.com> (raw)
In-Reply-To: <20090705184849.GA15042@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Sun, Jul 05, 2009 at 02:35:43PM +0200, Mark Kettenis wrote:
>> I also think you should add a comment about the specific ordering of
>> this unwinder.  It has to come before the dwarf2 unwinder because GCC
>> doesn't provide proper CFI for the epilogue, right?
> 
> Right - I would like to have a way to suppress this unwinder, maybe
> based on the producer string like other recognized dwarf2-frame
> quirks, but we can worry about that later.  I hope it will be
> unnecessary with GCC 4.5.

I would like that too -- maybe you can point me at an example?

I'm thinking that even if GCC 4.5 fixes the issue, people will
continue to use older GCCs for a while.



  reply	other threads:[~2009-07-05 20:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-04  0:26 Michael Snyder
2009-07-04  0:37 ` Michael Snyder
2009-07-05 10:54   ` Hui Zhu
2009-07-05 12:36   ` Mark Kettenis
2009-07-05 18:49     ` Daniel Jacobowitz
2009-07-05 20:46       ` Michael Snyder [this message]
2009-07-05 21:12         ` Daniel Jacobowitz
2009-07-05 20:58     ` Michael Snyder
2009-07-11 20:19       ` Michael Snyder
2009-07-12 17:07         ` Mark Kettenis
2009-07-12 17:53           ` Michael Snyder
2009-07-13  4:55             ` drow
2009-07-13 19:43               ` Michael Snyder
2009-07-13 19:44                 ` Daniel Jacobowitz
2009-07-13 20:28                   ` Michael Snyder
2009-07-13 20:20                 ` Mark Kettenis

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=4A51105D.5010400@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=teawater@gmail.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