This is the mail archive of the mailing list for the frysk project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bi-arch test patch for 64-bit frysk

Yong Zheng wrote:

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)

on ppc64, testGetAuxv fails in 32-bit testcase because there are three AT_NULL at the end of aux vectors, which might be actually ok (because I don't see any nagative impact it can bring up). I don't know what is the situation in x86_64. But I guess it is the same. GDB encounters the same problem for 32-bit application on ppc64. Roland had a fix for that, but I don't verify yet. I can code a patch in Frysk's side tomorrow morning.

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)

I guess this is the same problem with 32-bit testExecSyscall on ppc64: syscall tracer don't get correctly the syscall number. Something in EM64T ISA need to be changed to support 32-bit target well I guess.

BTW, one thing confusing me is that why it is named EM64T, and not X86_64. Just curious anyway. :-)

- Wu Zhou

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]