From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/12642] utrace: taskfinder misses events when main thread does not go through at least one quiesce
Date: Sat, 03 Nov 2012 17:03:00 -0000 [thread overview]
Message-ID: <bug-12642-6586-PpGlXoI2vi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12642-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12642
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #4 from Josh Stone <jistone at redhat dot com> 2012-11-03 17:02:56 UTC ---
(In reply to comment #3)
> 4) The new dyninst runtime ("--runtime=dyninst") uses the dyninst library to
> attach, which ends up using ptrace. Attaching to a running process isn't quite
> there yet, but I think it should be possible to interrupt a system call.
I'd be surprised if there was a quiesce-type issue in stapdyn, but I did find
an obvious omission that caused its attach to miss -- commit 02bff02.
--
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:[~2012-11-03 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 6:05 [Bug runtime/12642] New: " raysonlogin at gmail dot com
2012-10-29 12:57 ` [Bug runtime/12642] " fche at redhat dot com
2012-10-29 19:43 ` mjw at redhat dot com
2012-11-02 16:04 ` dsmith at redhat dot com
2012-11-03 17:03 ` jistone at redhat dot com [this message]
2012-11-27 15:36 ` dsmith at redhat dot com
2012-12-06 20:06 ` dsmith at redhat dot com
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-12642-6586-PpGlXoI2vi@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).