This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Strange stepping behaviour with PPC 32 and secure PLTs
- From: Daniel Jacobowitz <drow at false dot org>
- To: PAUL GILLIAM <pgilliam at us dot ibm dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 11 May 2006 22:29:12 -0400
- Subject: Re: Strange stepping behaviour with PPC 32 and secure PLTs
- References: <1143758781.21920.464.camel@dufur.beaverton.ibm.com> <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