From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18296 invoked by alias); 22 May 2009 20:45:21 -0000 Received: (qmail 18141 invoked by uid 48); 22 May 2009 20:45:06 -0000 Date: Fri, 22 May 2009 20:45:00 -0000 From: "jistone at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20090522204505.10189.jistone@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/10189] New: STP_START gets lost in a warning flood X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q2/txt/msg00679.txt.bz2 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.