This is the mail archive of the
mailing list for the elfutils project.
Re: dwfl_module_addrinfo and @plt entries
- From: Mark Wielaard <mark at klomp dot org>
- To: Milian Wolff <mail at milianw dot de>
- Cc: elfutils-devel at sourceware dot org
- Date: Fri, 6 Jan 2017 20:17:53 +0100
- Subject: Re: dwfl_module_addrinfo and @plt entries
- Authentication-results: sourceware.org; auth=none
- References: <4389913.7LHyNoxDn3@agathebauer> <20170104134223.GN2187@stream> <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_
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 :)