From: Alan Modra <amodra@bigpond.net.au>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Strange stepping behaviour with ppc32 with secure PLTs
Date: Sat, 20 May 2006 01:32:00 -0000 [thread overview]
Message-ID: <20060520011451.GE22757@bubble.grove.modra.org> (raw)
In-Reply-To: <1148055854.315.5.camel@dufur.beaverton.ibm.com>
On Fri, May 19, 2006 at 09:24:14AM -0700, PAUL GILLIAM wrote:
> Hold the presses! Could the fact that the libc being used does not have
> a '.symtab' section be the cause of the problem? For some reason, the
> library I was using has a '.dynsym' section, but no '.symtab' section.
> I suspect that someone was trying to save some disc space and caused
> several problems.
>
> The routine 'bfd_get_synthetic_symtab' takes both static and dynamic
> symbol tables as input. So it's no wonder it's not doing the right
> thing if one is missing.
No. ppc32 uses the generic _bfd_elf_get_synthetic_symtab, which only
uses the dyn syms. The only target to use both sym tables is ppc64,
where synthetic syms are handy for disassembly of relocatable object
files (which don't have a dynamic sym table).
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2006-05-20 1:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 22:50 PAUL GILLIAM
2006-05-12 23:12 ` Daniel Jacobowitz
2006-05-13 1:46 ` PAUL GILLIAM
2006-05-13 14:58 ` Alan Modra
2006-05-13 15:13 ` Daniel Jacobowitz
2006-05-15 3:34 ` Alan Modra
2006-05-15 15:10 ` Daniel Jacobowitz
2006-05-16 2:07 ` Alan Modra
2006-05-16 2:35 ` Daniel Jacobowitz
2006-05-16 7:18 ` Mark Kettenis
2006-05-16 17:53 ` Alan Modra
2006-05-19 17:38 ` PAUL GILLIAM
2006-05-20 1:32 ` Alan Modra [this message]
2006-06-23 21:06 ` PAUL GILLIAM
2006-06-23 21:22 ` Daniel Jacobowitz
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=20060520011451.GE22757@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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