This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/17359] systemtap in dyninst mode fails to hit PLT probes
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 16 Sep 2015 22:20:13 +0000
- Subject: [Bug dyninst/17359] systemtap in dyninst mode fails to hit PLT probes
- Auto-submitted: auto-generated
- References: <bug-17359-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17359
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
Yes, I'm not surprised. Dyninst does instruction-level analysis to determine
how to safely relocate code for instrumentation. But indirect jumps are opaque
control flow to this analysis, and usually Dyninst just decides it's unsafe to
proceed. In theory it would be fine, since we do know this is well-behaved, so
perhaps Dyninst could learn a heuristic to identify and allow PLT
instrumentation.
--
You are receiving this mail because:
You are the assignee for the bug.