This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/17352] probing by pid using --runtime=dyninst not having -x or -c set
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 05 Sep 2014 16:37:24 +0000
- Subject: [Bug dyninst/17352] probing by pid using --runtime=dyninst not having -x or -c set
- Auto-submitted: auto-generated
- References: <bug-17352-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17352
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|runtime |dyninst
Severity|normal |enhancement
--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
Right, the dyninst mode is not system-wide like the kernel -- we have to
explicitly attach to processes. Right now we choose to simply attach to the
-x/-c process and any children we see forked after that. I suppose we could
attempt additional attachments based on the process(PID) probes in the script.
However, I think we may have other issues internally in the way the PID is
encoded, overloading the offset field. That works fine for
process(PID).begin/end, but we'll need a true offset for .function to work. It
looks like the call to dynprobe_add_uprobe() is currently ignoring any PID.
(These process(PID) uprobe types are new in 2.6, so they weren't a
consideration when this stapdyn code was written.)
--
You are receiving this mail because:
You are the assignee for the bug.