From: Michael Eager <eager@eagerm.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb@sourceware.org, Alan Modra <amodra@gmail.com>
Subject: Re: PowerPC SecurePLT - stepping into library function
Date: Fri, 06 Jan 2012 20:27:00 -0000 [thread overview]
Message-ID: <4F075902.1020500@eagerm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1201062006460.25738@digraph.polyomino.org.uk>
On 01/06/2012 12:09 PM, Joseph S. Myers wrote:
> On Fri, 6 Jan 2012, Michael Eager wrote:
>
>> It seems that the best way to fix this would be to create
>> a new OSABI sniffer for SecurePLT which identifies that
>> the executable was compiled with -msecurePLT. One issue
>> is how to identify these programs. The Power Arch 32-bit ABI
>> (Sect 5.2.5.2, note at end) says that these will have
>> R_PPC_REL16 relocations. I don't see any of these relocs.
>
> That's about relocatable objects, i.e. static relocations in .o files, not
> dynamic relocations in executables and shared libraries.
I didn't see any in the .o files, either.
>> Is there any possibility of a chimera: an executable compiled
>> using Secure PLT linking to libraries which use the old style
>> PLT? Or vice-versa? I'm assuming that this cannot happen.
>
> As far as I know that ought to work.
Yeah, that's what I was afraid of. That means that an OSABI
sniffer will not work.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2012-01-06 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 19:54 Michael Eager
2012-01-06 20:09 ` Joseph S. Myers
2012-01-06 20:27 ` Michael Eager [this message]
2012-01-06 20:15 ` Mark Kettenis
2012-01-06 20:24 ` Michael Eager
2012-01-06 20:56 ` Mark Kettenis
2012-01-07 20:57 ` Michael Eager
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=4F075902.1020500@eagerm.com \
--to=eager@eagerm.com \
--cc=amodra@gmail.com \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.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