From: Daniel Jacobowitz <drow@false.org>
To: Alan Modra <amodra@bigpond.net.au>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix powerpc64-linux inferior function calls
Date: Sun, 02 Oct 2005 22:31:00 -0000 [thread overview]
Message-ID: <20051002223118.GC32728@nevyn.them.org> (raw)
In-Reply-To: <20050928073345.GK29044@bubble.grove.modra.org>
On Wed, Sep 28, 2005 at 05:03:45PM +0930, Alan Modra wrote:
> This gives me a gdb that can make inferior calls on powerpc64-linux when
> debugging code compiled by a gcc that doesn't provide dot-symbols.
> ppc-sysv-tdep.c:convert_code_addr_to_desc_addr needs dot-symbols to find
> the function descriptor corresponding to a given pc.
>
> It's a band-aid really. I think the proper fix is to not convert
> function pointers to function code addresses in gdb's expression
> evaluator, which would keep the pointer to the descriptor. This of
> course would mean that gdb's breakpoint and similar code expecting that
> function symbols point to code would need adjusting. One benefit would
> be that "p *func" would print me the descriptor, which is what I'd
> expect for powerpc64.
>
> PR 2016
> * elfread.c (elf_symtab_process): Split out from..
> (elf_symtab_read): ..here.
> (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? 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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-02 22:31 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 [this message]
2005-10-02 23:22 ` Alan Modra
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=20051002223118.GC32728@nevyn.them.org \
--to=drow@false.org \
--cc=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