This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Re: bi-arch test patch for 64-bit frysk
- From: Yong Zheng <zhengyo at cn dot ibm dot com>
- To: frysk at sourceware dot org
- Date: Thu, 24 Aug 2006 19:38:12 +0800
- Subject: Re: bi-arch test patch for 64-bit frysk
- References: <1156413940.2172.63.camel@YZ_X86_64>
hi,
The followings are some difference between the test results of cases in
64-bit mode and in 32-bit mode on 64-bit frysk.
All tests are based on the cvs head(08-24).
On X86_64, the following cases fail in 32-bit mode but pass in 64-bit
mode on 64-bit frysk:
1)testGetAuxv(frysk.proc.TestProcGet)java.lang.RuntimeException: unknown
word size for auxv (1|32l|64l|32b|64b 10000)
at frysk.sys.proc.AuxvBuilder.construct(TestRunner)
2)testProcRefresh(frysk.proc.TestRefresh)junit.framework.AssertionFailedError: event loop run explictly stopped (assertSendDelCloneWaitForAcks (Sig_USR2))
at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
3)testExecSyscall(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError: Caught exec syscall expected:<false> but was:<true>
at frysk.proc.TestTaskSyscallObserver.testExecSyscall(TestRunner)
4)testX8664Modify(frysk.proc.TestX8664Modify)junit.framework.AssertionFailedError: unexpected signal 30
5)testCloneSyscall(frysk.proc.TestTaskSyscallObserver)java.lang.RuntimeException: clone's parent in unexpected state syscallRunning at frysk.proc.TaskState.clonedState(TestRunner)
On PPC64, the following cases fail in 32-bit mode but pass in 64-bit
mode on 64-bit frysk:
1)testGetAuxv(frysk.proc.TestProcGet)java.lang.RuntimeException: unknown
word size for auxv (1|32l|64l|32b|64b 10000)
2)testExecSyscall(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError: Caught exec syscall expected:<false> but was:<true>
3)testSyscallOpen(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError: attempt to open a.file
Best regards
Yong Zheng