public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Milian Wolff <>
Subject: Re: dwfl_module_addrinfo and @plt entries
Date: Wed, 04 Jan 2017 13:42:00 -0000	[thread overview]
Message-ID: <20170104134223.GN2187@stream> (raw)
In-Reply-To: <4389913.7LHyNoxDn3@agathebauer>

On Wed, Jan 04, 2017 at 01:41:26AM +0100, Milian Wolff wrote:
> how do I get symbol information for @plt entries?

Short answer. You cannot with the dwfl_module_getsym/addr*
functions. And we don't have accessors for "fake" symbols
(yet). Sorry.

Longer answer. An address pointing into the PLT does
really point to an ELF symbol. The PLT/GOT contains entries
that are architecture specific "jump targets" that contain
(self-modifying) code/data on first access. A PLT entry
is code that sets up the correct (absolute) address of
a function on first access. And on second access it fetches
that function address and jumps to it. Since this is
architecture specific we would need a backend function
that translates an address pointing into the PLT into
an actual function address. You would then be able to
fetch the actual ELF symbol that address is associated

If we have such a backend function then we could even
do what BFD apparently does. Which is to then create a
"fake" symbol with as name real_function@plt. But I am
not sure such fake symbols are very useful (and will
quickly become confusing since they aren't real ELF

Hope that helps. And maybe inspires someone (you?) to
write up such a backend function and corresponding
dwfl frontend function.



  reply	other threads:[~2017-01-04 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  0:41 Milian Wolff
2017-01-04 13:42 ` Mark Wielaard [this message]
2017-01-06 10:28   ` Milian Wolff
2017-01-06 19:17     ` Mark Wielaard
2017-07-05 13:34       ` Milian Wolff
2017-07-07 11:03         ` Mark Wielaard
2017-07-10 11:06           ` Milian Wolff
2017-08-28 14:28             ` Milian Wolff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170104134223.GN2187@stream \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).