From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13187] Reconsider the semantics of process(number).thread.begin/end
Date: Wed, 14 Sep 2011 14:31:00 -0000 [thread overview]
Message-ID: <bug-13187-6586-bMiW7syYkp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2011-09-14 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 21:11 [Bug translator/13187] New: " brolley at redhat dot com
2011-09-14 14:31 ` dsmith at redhat dot com [this message]
2016-05-26 17:57 ` [Bug translator/13187] " fche at redhat dot com
2011-09-14 18:23 Dave Brolley
2011-09-21 19:46 ` David Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13187-6586-bMiW7syYkp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).