This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/18143] target_set tapset does not track threads created with clone()
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 19 Mar 2015 18:28:01 +0000
- Subject: [Bug tapsets/18143] target_set tapset does not track threads created with clone()
- Auto-submitted: auto-generated
- References: <bug-18143-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18143
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
Hmm, I'm confused. The following commit (present in stap 2.6) changed
target_set.stp to use process.begin and process.end, instead of syscall.fork.
So, in theory you shouldn't be seeing the problem you are seeing.
====
commit a7160c2becb70d91da0cf3f7ac08614ee0950f71
Author: Josh Stone <jistone@redhat.com>
Date: Thu May 16 16:12:02 2013 -0700
Improve the kernel target_set.stp and add a stapdyn version
* tapset/linux/target_set.stp: Prefer process.begin/end for better
tracking *process* lifetime. (syscall.exit covers thread exits too!)
* tapset/dyninst/target_set.stp: Implement stapdyn target_set.
* testsuite/systemtap.base/target_set_thread.*: Test that thread exits
don't cause target_set to lose sight of a process.
* main.cxx (run_sdt_benchmark): Save the timing info for verbose runs.
====
Does your version of stap 2.6 not have this patch?
--
You are receiving this mail because:
You are the assignee for the bug.