This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/10189] New: STP_START gets lost in a warning flood
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 22 May 2009 20:45:06 -0000
- Subject: [Bug runtime/10189] New: STP_START gets lost in a warning flood
- Reply-to: sourceware-bugzilla at sourceware dot org
This command will stall:
stap -e 'probe begin { while (++i<100) warn("something is wrong!") }' -c true
Such a warning flood can happen, for example, when a lot of kernel.function or
kprobe.function probes fail to register. The script is supposed to continue
anyway, but in this case the child process is waiting for a SIGUSR1 before it
begins. That signal should be sent on an STP_START control message, but
debugging reveals that STP_START is never seen by stapio.
I suspect that the control channel is overflowing with STP_OOB_DATA for the
warnings, and so the STP_START is dropped.
--
Summary: STP_START gets lost in a warning flood
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jistone at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10189
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.