From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: aristovski@qnx.com
Cc: gdb@sourceware.org
Subject: Re: Frame lost after 'leave' and before 'ret' instruction on i386?
Date: Fri, 16 May 2008 17:48:00 -0000 [thread overview]
Message-ID: <200805161748.m4GHmRdR000890@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <482DC452.1020102@qnx.com> (message from Aleksandar Ristovski on Fri, 16 May 2008 13:28:50 -0400)
> Date: Fri, 16 May 2008 13:28:50 -0400
> From: Aleksandar Ristovski <aristovski@qnx.com>
>
> Mark Kettenis wrote:
> > The compiler is supposed to give us unwind info for the function's
> > epilogue, but unfortunately GCC doesn't. There's not much we can do
> > about it in GDB. Fortunately it isnt an issue that users see a lot.
> >
>
> Out of curiosity: what is the problem with specifying epilogue? Am I
> wrong when I say that there can be only so many epilogue types
> (i.e. compiler will not generate infinite number of epilogues)?
> Therefore, only one index in a 'epilogue description table' would
> suffice...
>
> (or am I over-simplifying?)
A compiler may reschedule instructions into the epilogue (this is what
makes writing prologue analyzers quite difficult). I don't know
whether GCC does that or not.
I guess the real problem is that nobody has been motivated enough to
fix the problem.
Better ask questions on the GCC mailing lists though if you want an
answer that's not just a guess ;).
prev parent reply other threads:[~2008-05-16 17:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 15:32 Aleksandar Ristovski
2008-05-16 15:58 ` Daniel Jacobowitz
2008-05-16 16:02 ` Aleksandar Ristovski
2008-05-16 16:09 ` Daniel Jacobowitz
2008-05-22 14:29 ` Aleksandar Ristovski
2008-05-22 14:40 ` Aleksandar Ristovski
2008-05-22 14:50 ` Daniel Jacobowitz
2008-05-22 15:05 ` Aleksandar Ristovski
2008-05-22 16:00 ` Aleksandar Ristovski
2008-05-22 16:02 ` Daniel Jacobowitz
2008-05-23 15:19 ` Aleksandar Ristovski
2008-05-22 18:06 ` Aleksandar Ristovski
2008-05-23 17:11 ` Daniel Jacobowitz
2008-05-23 17:23 ` Michael Snyder
2008-05-26 23:08 ` Aleksandar Ristovski
2008-05-27 21:33 ` Aleksandar Ristovski
2008-05-29 6:21 ` Thiago Jung Bauermann
2008-05-29 6:22 ` Aleksandar Ristovski
2008-06-04 13:12 ` Aleksandar Ristovski
2008-06-05 20:12 ` Mark Kettenis
2008-05-16 17:24 ` Mark Kettenis
2008-05-16 17:28 ` Aleksandar Ristovski
2008-05-16 17:47 ` Daniel Jacobowitz
2008-05-16 17:48 ` Mark Kettenis [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=200805161748.m4GHmRdR000890@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=aristovski@qnx.com \
--cc=gdb@sourceware.org \
/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