public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Milian Wolff <>
Subject: Re: dwfl_module_addrinfo and @plt entries
Date: Fri, 06 Jan 2017 19:17:00 -0000	[thread overview]
Message-ID: <20170106191753.GB8669@stream> (raw)
In-Reply-To: <4367790.cbajsgPFcv@milian-kdab2>

On Fri, Jan 06, 2017 at 11:28:25AM +0100, Milian Wolff wrote:
> On Wednesday, January 4, 2017 2:42:23 PM CET Mark Wielaard wrote:
> > Longer answer. An address pointing into the PLT does
> > really point to an ELF symbol.
> You mean: does _not_
> Right?

Yes, I meant "does not point".

> > 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
> > symbols).
> So the objdump command I used is leveraging BFD internally to give me the @plt 
> names? I noticed that I also see @plt in perf, which is also probably using 
> BFD internally. That at least clarifies why it works in some tools but not in 
> when using dwfl.

binutils objdump certainly does.

> > Hope that helps. And maybe inspires someone (you?) to
> > write up such a backend function and corresponding
> > dwfl frontend function.
> It does help, thanks. I'm interested in contributing such functionality, but, 
> sadly, I'm not sure when I'll get the time to actually do it.

Thanks, wish I had spare time myself :)



  reply	other threads:[~2017-01-06 19:17 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
2017-01-06 10:28   ` Milian Wolff
2017-01-06 19:17     ` Mark Wielaard [this message]
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=20170106191753.GB8669@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).