This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: probing a plt
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Stan Cox <scox at redhat dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Fri, 02 Sep 2011 17:21:16 -0400
- Subject: Re: probing a plt
- References: <4E6121E1.6040305@redhat.com>
Stan Cox <scox@redhat.com> writes:
> This is small example showing how a plt may possibly be probed.
Looks like a good start!
> [...] Currently the only possibility is probing every plt entry in a
> module. Suggestions for further refinements? [...]
> probe process("./12215.x").plt {printf ("plt-entry=%s\n",$$name)}
The natural one is to parametrize .plt() with the entry name/wildcard,
which should be available (since you're returning it for $$name). (It
might also be useful to support .plt(N) for table index N.)
A later step could be to use that name as a heuristic lookup into
libraries that may resolve the same-named function, to find some
possibly-applicable dwarf location data for resolving $context
variables.
- FChE