From: Daniel Jacobowitz <drow@false.org>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: Strange stepping behaviour with PPC 32 and secure PLTs
Date: Fri, 12 May 2006 08:37:00 -0000 [thread overview]
Message-ID: <20060512022912.GA24549@nevyn.them.org> (raw)
In-Reply-To: <1147389317.3672.46.camel@dufur.beaverton.ibm.com>
On Thu, May 11, 2006 at 04:15:17PM -0700, PAUL GILLIAM wrote:
> One way to fix this is for BFD to synthesize a new symbol in addition to 'foo@plt', let's
> say we call it 'foo@stub'. This new symbol would be in the '.text' section and would
> be found by lookup_minimal_symbol_by_pc_section() and all would be well. BFD would know
> that such a symbol should be generated if it was dealing with a ppc32 object file whose
> '.plt' section was not executable.
>
> I would rather have a GDB only solution.
Why?
The BFD solution is much more useful: it will make disassembly have
useful labels in both objdump and gdb when stopped in a stub.
rs6000_skip_trampoline_code may also be involved.
> A possibility would be to change lookup_minimal_symbol_by_pc_section() so that a symbol in
> the 'unknown' section would not be ignored if it was of type 'mst_solib_trampoline'.
What do you mean by "unknown section"?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-05-12 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 6:55 Strange stepping behaviour with PPC 64 " PAUL GILLIAM
2006-05-12 5:49 ` Strange stepping behaviour with PPC 32 " PAUL GILLIAM
2006-05-12 8:37 ` Daniel Jacobowitz [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=20060512022912.GA24549@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=pgilliam@us.ibm.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