From: Roland McGrath <roland@hack.frob.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: elfutils-devel@lists.fedorahosted.org,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [2/3, ppc64, elfutils patch] eu-strip vs. func addresses for GDB inferior calls
Date: Thu, 24 Mar 2011 10:44:00 -0000 [thread overview]
Message-ID: <20110324035149.429782C247@topped-with-meat.com> (raw)
In-Reply-To: Jan Kratochvil's message of Wednesday, 23 March 2011 18:21:32 +0100 <20110323172132.GA18225@host1.jankratochvil.net>
> the synthetic `.funcname' instructions-pointing symbols are generated on ppc64
> by BFD on its own from the function descriptor ELF symbols `funcname'.
I see. There were previous variants of the ppc64 tools (and perhaps
still are modes) in which actual .funcname symbols were defined as
well. I suspect that history is why BFD is organized this way.
> (DWARF symbols `funcname' point to the instructions which may be confusing.)
It is confusing if you use a noncanonical term like "DWARF symbol". In
DWARF, there are well-defined entities like DIEs that have well-defined
attributes that are specifically about PC values, and so none of that is
confusing on its own. It is just wrong to imagine that DWARF defines
something called a symbol that is akin to an ELF symbol.
> I agree it is only a workaround of the BFD design.
Then BFD should just be fixed.
Alan surely knows more about this particular stuff than anyone else.
His suggestions about BFD and GDB internals are probably the most useful.
Thanks,
Roland
next prev parent reply other threads:[~2011-03-24 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 15:49 Jan Kratochvil
2011-03-23 17:16 ` Roland McGrath
2011-03-23 18:05 ` Jan Kratochvil
2011-03-24 3:09 ` Alan Modra
2011-04-04 11:19 ` obsolete: " Jan Kratochvil
2011-03-24 10:44 ` Roland McGrath [this message]
2011-03-23 22:18 ` Ulrich Drepper
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=20110324035149.429782C247@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=binutils@sourceware.org \
--cc=elfutils-devel@lists.fedorahosted.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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