From: Alan Modra <amodra@bigpond.net.au>
To: gdb-patches@sources.redhat.com
Subject: Re: Fix powerpc64-linux inferior function calls
Date: Sun, 02 Oct 2005 23:22:00 -0000 [thread overview]
Message-ID: <20051002232228.GB26007@bubble.grove.modra.org> (raw)
In-Reply-To: <20051002223118.GC32728@nevyn.them.org>
On Sun, Oct 02, 2005 at 06:31:18PM -0400, Daniel Jacobowitz wrote:
> > (elf_symfile_read): Read both static and dynamic symbols before
> > processing. Call bfd_get_synthetic_symtab.
>
> Why do we need to read both before processing either?
The powerpc64 get_synthetic_symtab will use both dynamic and static
symbol tables. Handy when debugging stripped objects. So both symbols
tables need to be read before calling bfd_get_synthetic_symtab.
> I'm thinking of
> the patch I posted here:
> http://sourceware.org/ml/gdb-patches/2005-06/msg00220.html
> and pinged a few weeks ago.
Which I see you do in this patch too. I didn't know about your patch
when I wrote mine.. The order of processing doesn't matter at all.
It just fell out that way in my patch. Incidentally, why did you
need to fudge the synthetic syms?
+ /* Synthetic symbols are not, strictly speaking, either local
+ or global. But we can treat them as global symbols, since
+ they are effectively dynamic symbols. */
+ synth_symbol_table[i]->flags |= BSF_GLOBAL;
Seems like this should be done in bfd if necessary.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-10-02 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 7:34 Alan Modra
2005-10-02 22:31 ` Daniel Jacobowitz
2005-10-02 23:22 ` Alan Modra [this message]
2005-10-02 23:48 ` Daniel Jacobowitz
2005-10-03 0:35 ` Alan Modra
2005-10-03 1:04 ` Daniel Jacobowitz
2005-10-03 3:32 ` Alan Modra
2005-10-03 4:40 ` Daniel Jacobowitz
2005-10-03 8:20 ` Alan Modra
2006-03-03 14:04 ` David Lecomber
2006-03-03 14:11 ` David Lecomber
2006-03-30 9:53 ` 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=20051002232228.GB26007@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=gdb-patches@sources.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