From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20662 invoked by alias); 26 Mar 2008 11:12:49 -0000 Received: (qmail 20647 invoked by uid 22791); 26 Mar 2008 11:12:48 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 26 Mar 2008 11:12:25 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1JeTYM-0006zk-3Z; Wed, 26 Mar 2008 12:12:22 +0100 Subject: Re: [SCM] master: Add INFO log-level; use warning level instead of System.out.println. From: Mark Wielaard To: frysk@sourceware.org Cc: Andrew Cagney In-Reply-To: <1205750862.7607.35.camel@localhost.localdomain> References: <20080313192850.25428.qmail@sourceware.org> <1205492803.27548.33.camel@dijkstra.wildebeest.org> <1205750862.7607.35.camel@localhost.localdomain> Content-Type: text/plain Date: Wed, 26 Mar 2008 11:12:00 -0000 Message-Id: <1206529941.3553.24.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00181.txt.bz2 Hi Andrew, On Mon, 2008-03-17 at 11:47 +0100, Mark Wielaard wrote: > > > I am also seeing the following since yesterday: > > > > 2) testBlockingFibonacciClone(frysk.proc.live.TestTaskObserverBlocked)java.lang.RuntimeException: {frysk.proc.live.LinuxPtraceTask@319faf55,pid=18639,tid=18640,state=detached} in state "detached" did not handle handleStoppedEvent SIGSTOP(19) > > at frysk.proc.live.State.unhandled(TestRunner) > > at frysk.proc.live.LinuxPtraceTaskState.handleStoppedEvent(TestRunner) > > at frysk.proc.live.LinuxPtraceTask.processStoppedEvent(TestRunner) > > at frysk.proc.live.LinuxWaitBuilder.stopped(TestRunner) > > at frysk.sys.Wait.wait(TestRunner) > > at frysk.sys.Wait.wait(TestRunner) > > at frysk.event.WaitEventLoop.block(TestRunner) > > at frysk.event.EventLoop.runEventLoop(TestRunner) > > at frysk.event.EventLoop.runPolling(TestRunner) > > at frysk.testbed.TestLib.assertRunUntilStop(TestRunner) > > at frysk.testbed.TestLib.assertRunUntilStop(TestRunner) > > at frysk.proc.live.TestTaskObserverBlocked.access$2(TestRunner) > > at frysk.proc.live.TestTaskObserverBlocked$BlockingFibonacci.(TestRunner) > > at frysk.proc.live.TestTaskObserverBlocked$1$CloneFibonacci.(TestRunner) > > at frysk.proc.live.TestTaskObserverBlocked.testBlockingFibonacciClone(TestRunner) > > at frysk.junit.Runner.runCases(TestRunner) > > at frysk.junit.Runner.runTestCases(TestRunner) > > at TestRunner.main(TestRunner) > > > > Which I haven't tracked down to a specific commit yet. Bugzilla has it > > as issue #3937. Might it be caused by one of your new StopEventLoop > > patches from yesterday? If you could explain what those new patches do > > that would be nice. > > I don't see this issue anymore. Do you know what fixed it? And could you > describe what your new StepEventLoop patches should accomplish? Still not reappeared, so I closed the bug report. If you could comment on whether your StepEventLoop patches might have been responsible for the fix and what they are intended for that would be appreciated. Thanks, Mark