This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/13187] Reconsider the semantics of process(number).thread.begin/end
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 14 Sep 2011 14:28:23 +0000
- Subject: [Bug translator/13187] Reconsider the semantics of process(number).thread.begin/end
- Auto-submitted: auto-generated
- References: <bug-13187-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13187
--- Comment #1 from David Smith <dsmith at redhat dot com> 2011-09-14 14:28:23 UTC ---
(In reply to comment #0)
> However, for a running process, these probes will currently never fire, because
> the task ids of the child threads do not match the given process id.
There is a situation where process(PID).thread.begin probes will fire.
- Start a process that creates several threads that will run for an extended
period of time. Determine the pids of those threads.
- RUn systemtap with a script that probes those pids.
- As systemtap attaches to those threads, the process(PID).thread.begin probe
will fire.
In my opinion, changing the semantics here is too big/messy of a change.
Instead, a new probe type, something like 'process(PATH/PID).thread.create',
could be created.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.