From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libc-alpha@sourceware.org, binutils@sourceware.org,
gdb@sourceware.org, Mark Wielaard <mjw@redhat.com>,
Frank Eigler <fche@redhat.com>
Subject: Re: RFC: Unwind info for PLT
Date: Fri, 10 Jun 2011 14:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1106101410480.1616@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20110610074524.GR17079@tyan-ft48-01.lab.bos.redhat.com>
On Fri, 10 Jun 2011, Jakub Jelinek wrote:
> Anyway, I think hardcoding this in the linker would be problematic,
> we couldn't tweak it, so providing some special hidden symbols around
> the .plt section and let glibc crtfiles provide it sounds like the best
> option to me.
I think that when the linker generates code it should generate unwind info
for it to allow accurate backtraces from any instruction (both .eh_frame
and .debug_frame, or target-specific forms on some targets). The details
of this generated code may not be part of the ABI on all targets, may vary
depending on the linker version and may be a lot more complicated than a
single PLT section - there are lots of purposes for which the linker may
generate code. I don't think glibc crtfiles are a good place for it.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-06-10 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 7:45 Jakub Jelinek
2011-06-10 14:11 ` Mark Kettenis
2011-06-10 14:17 ` Joseph S. Myers [this message]
2011-06-10 15:15 ` Richard Henderson
2011-06-13 17:14 ` Jakub Jelinek
2011-06-13 17:34 ` Richard Henderson
2011-06-13 20:54 ` Ian Lance Taylor
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=Pine.LNX.4.64.1106101410480.1616@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jakub@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mjw@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