From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org
Subject: Re: [RFC] Improve amd64 prologue analysis
Date: Thu, 25 Nov 2010 16:30:00 -0000 [thread overview]
Message-ID: <20101125163022.GI2634@adacore.com> (raw)
In-Reply-To: <201011251338.oAPDck2Y013525@glazunov.sibelius.xs4all.nl>
> > One last bit of information - which I got second hand, but hopefully
> > accurate. I think that the GCC team is on its way to generating the
> > unwinding info in that format, rather than the usual DWARF-based
> > eh_frame/debug_frame. So the Microsoft format should become the default
> > even for code generated by GCC... So eventually, I think we are going
> > to need to add an unwinder for that, even for GCC code.
>
> I certainly hope you're wrong here, since it would mean a massive ABI
> break on platforms currently using .eh_frame, and presumably would be
> x86-specific.
I should have said that this is only relevant to x86_64-windows.
All other platforms will continue to use the usual eh_frame, of
course.
--
Joel
next prev parent reply other threads:[~2010-11-25 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 17:28 Pierre Muller
2010-11-18 17:22 ` Joel Brobecker
2010-11-19 8:15 ` Pierre Muller
2010-11-19 17:20 ` Joel Brobecker
2010-11-19 22:50 ` Pierre Muller
2010-12-14 7:05 ` Joel Brobecker
2010-12-14 9:58 ` Pedro Alves
2010-12-15 23:07 ` Mark Kettenis
2010-12-16 4:15 ` Joel Brobecker
2010-11-24 21:19 ` Mark Kettenis
2010-11-24 22:15 ` Joel Brobecker
2010-11-24 22:26 ` Joel Brobecker
2010-11-25 13:39 ` Mark Kettenis
2010-11-25 16:30 ` Joel Brobecker [this message]
2010-11-25 19:19 ` Kai Tietz
2010-11-24 22:17 ` Joel Brobecker
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=20101125163022.GI2634@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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