Running frysk.rt.TestStepping.testStepSigRaise generates the above error, although the test case passes. The test case raises SIGUSR1 and handles it in a local signal handler. It is located in frysk/frysk-core/frysk/pkglibdir/funit-rt-sigraise.c
I may have been mistaken, as the test actually occasionally fails (happens considerably more often during make check, rather than running TestRunner directly). I'm not sure if this bug is the cause, but until I know more, I'll mark it broken pending resolution here.
It now fails as: 1) testStepSigRaise(frysk.stepping.TestStepping)java.lang.ArrayIndexOutOfBoundsException: 0 at frysk.stepping.TestStepping$AssertLine.runAssertions(TestRunner) at frysk.stepping.TestStepping$LockObserver.update(TestRunner) at java.util.Observable.notifyObservers(libgcj.so.8rh) at frysk.stepping.SteppingEngine$SteppingObserver.updateExecuted(TestRunner) at frysk.proc.Task.notifyInstruction(TestRunner) at frysk.proc.live.LinuxTaskState$Stepping.handleTrappedEvent(TestRunner) at frysk.proc.live.LinuxTask.processTrappedEvent(TestRunner) at frysk.proc.live.LinuxWaitBuilder.stopped(TestRunner) at frysk.sys.Wait.wait(TestRunner) at frysk.sys.Wait.waitAll(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.stepping.TestStepping.testStepSigRaise(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner)
The warning still happens from time to time. I suspect that it is seeing a double attach somehow. The warning is annoying because I was unable to track it fully down. The good news is that the the test mentioned does consistently PASS now. This was a more complex version the testFirstFrameInSignalHandler() test. The test needed to be adjusted slightly to make sure the first line of the signal handler was identified correctly: commit 6356571eaff4020746159c99704b3dbaa14bc221 Author: Mark Wielaard <mwielaard@redhat.com> Date: Thu Apr 17 23:33:53 2008 +0200 Don't mark TestStepping.testStepSigRaise() as unresolved bug #4237. frysk-core/frysk/pkglibdir/ChangeLog 2008-04-17 Mark Wielaard <mwielaard@redhat.com> * funit-rt-sigraise.c (handler): Make sure entry marker is really on first source line. frysk-core/frysk/stepping/ChangeLog 2008-04-17 Mark Wielaard <mwielaard@redhat.com> * TestStepping.java (testStepSigRaise): Don't mark unresolved #4237. Leaving bug open because the warning is still annoying as long as we haven't figured out where the extra stop event is coming from.