This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/6841] system-wide utrace syscall tracing script don't respond signal
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 14 Aug 2008 20:52:09 -0000
- Subject: [Bug uprobes/6841] system-wide utrace syscall tracing script don't respond signal
- References: <20080813164019.6841.mhiramat@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mhiramat at redhat dot com 2008-08-14 20:52 -------
(In reply to comment #3)
> I've reproduced this on 2.6.25.14-108.fc9.x86_64. With the addition of a timer
> probe that exists after 5 seconds, the script exits correctly.
I checked too. stapio is working, just fails to receive signals.
> One possible fix would be to exclude stapio from system-wide probing.
I think we should dig this issue deeper, and find the root cause of the issue.
If we could ensure that this issue *only* affects to "host" stapio, excluding
stapio will be acceptable.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6841
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.