For -arch 32: testStepSigReturn(frysk.proc.TestTaskObserverInstructionSigReturn)junit.framework.AssertionFailedError: Wrong signal received: 5 at frysk.proc.TestTaskObserverInstructionSigReturn.updateSignaled(TestRunner) at frysk.proc.Task.notifySignaled(TestRunner) at frysk.proc.live.LinuxTaskState$Running.handleSignaledEvent(TestRunner) at frysk.proc.live.LinuxTaskState$Stepping.handleSignaledEvent(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.proc.TestTaskObserverInstructionSigReturn.testStepSigReturn(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) the log shows: FINE: entering peekFully, caret: 0x380, off: 0x0, len: 0x4 28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully FINE: exiting peekFully 28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully FINE: entering peekFully, caret: 0x80, off: 0x0, len: 0x4 28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully FINE: exiting peekFully 28-Dec-07 10:32:19 PM frysk.proc.Task notifyCodeBreakpoint FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} notifyCodeBreakpoint(134,514,034) 28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully FINE: entering peekFully, caret: 0x80, off: 0x0, len: 0x4 28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully FINE: exiting peekFully 28-Dec-07 10:32:19 PM frysk.proc.Task getMemory FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} entering get memory frysk.proc.live.LogicalMemoryBuffer@2f89d735 28-Dec-07 10:32:19 PM frysk.proc.Task getMemory FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} exiting get memory frysk.proc.live.LogicalMemoryBuffer@2f89d735 28-Dec-07 10:32:19 PM frysk.proc.live.LinuxTaskState$Stepping handleSignaledEvent FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} handleSignaledEvent, signal: 5 28-Dec-07 10:32:19 PM frysk.proc.live.LinuxTaskState$Running handleSignaledEvent FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} handleSignaledEvent, signal: 5 28-Dec-07 10:32:19 PM frysk.proc.Task notifySignaled FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping} notifySignaled(int) -- notice reasoning that it got a sig-trap for no reason. machine is amd64 running kernel 2.6.23.9-85.fc8; doesn't occur on intel64 running kernel 2.6.23.1-42.fc8
It's a stray SIGTRAP after a sig-return. Why it only appears to occur on amd?