From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Richard Smith <richard@ex-parrot.com>
Cc: gdb@sourceware.org
Subject: Re: Backtraces broken on i386 by unorthodox encoding of push %ebp
Date: Sun, 31 Mar 2013 05:48:00 -0000 [thread overview]
Message-ID: <20130331054825.GA2537@host2.jankratochvil.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1303302037420.2445@sphinx.mythic-beasts.com>
On Sat, 30 Mar 2013 22:02:55 +0100, Richard Smith wrote:
> Yes, you're right, I could quite easily. But a design criterion for
> this project is that it is easy for third-parties to produce
> backtraces from production code (i.e. once debugging information has
> been stripped).
It should be in .eh_frame - which is also used for exceptions unwinding if
an exception is thrown through this frame. .eh_frame is runtime information,
it is in a mapped segment and never stripped.
Jan
prev parent reply other threads:[~2013-03-31 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 19:13 Richard Smith
2013-03-30 19:50 ` Jan Kratochvil
2013-03-30 20:07 ` Joel Brobecker
2013-03-30 21:03 ` Richard Smith
2013-03-30 23:53 ` Mike Frysinger
2013-03-31 5:48 ` Jan Kratochvil [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=20130331054825.GA2537@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=richard@ex-parrot.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