During merging Test<ISA>Regs.java into one case TestRegs.java, we found one nasty bug. After building frysk, run the following commands: #cd $BUILD/frysk-core #./TestRunner -l FINE frysk.proc.TestX8664Regs The case will pass. The case will pass even if you run "TestRunner -l FINE" under $BUILD/frysk-core. However, if you modify the running sequence of TestX8664Regs in $BUILD/frysk-core/frysk/core/JUnitTests.java from: list.add(frysk.proc.TestRun.class); list.add(frysk.proc.TestTaskClonedObserver.class); list.add(frysk.proc.TestTaskForkedObserver.class); list.add(frysk.proc.TestTaskObserverBlocked.class); list.add(frysk.proc.TestTaskObserverDetach.class); list.add(frysk.proc.TestTaskObserver.class); list.add(frysk.proc.TestTaskSyscallObserver.class); list.add(frysk.proc.TestTaskTerminateObserver.class); list.add(frysk.proc.TestX8664Modify.class); list.add(frysk.proc.TestX8664Regs.class); to: list.add(frysk.proc.TestX8664Regs.class); list.add(frysk.proc.TestRun.class); list.add(frysk.proc.TestTaskClonedObserver.class); list.add(frysk.proc.TestTaskForkedObserver.class); list.add(frysk.proc.TestTaskObserverBlocked.class); list.add(frysk.proc.TestTaskObserverDetach.class); list.add(frysk.proc.TestTaskObserver.class); list.add(frysk.proc.TestTaskSyscallObserver.class); list.add(frysk.proc.TestTaskTerminateObserver.class); list.add(frysk.proc.TestX8664Modify.class); . Then you will get the bug like the following: Running testX8664Regs(frysk.proc.TestX8664Regs) ...PASS Running testCreateAttachedContinuedProc(frysk.proc.TestRun) ...PASS Running testCreateAttachedStoppedProc(frysk.proc.TestRun) ...PASS Running testTaskCloneObserver(frysk.proc.TestTaskClonedObserver) ...FAIL junit.framework.AssertionFailedError: event loop run explictly stopped (startChild (Sig_USR1)) Running testTaskForkedObserver(frysk.proc.TestTaskForkedObserver) ...FAIL junit.framework.AssertionFailedError: event loop run explictly stopped (startChild (Sig_USR1)) .....
Created attachment 1257 [details] The modified TestX8664Regs.java.
After we did some modification on TestX8664Regs.java, the bug can be fixed but we do not know what caused the bug. see the above attached file. (In reply to comment #1) > Created an attachment (id=1257) > The modified TestX8664Regs.java. >