Bug 5432 - testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError: Memory Buffer Capacity: expected:<4294967295> but was:<-1>
Summary: testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.Asser...
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-29 10:35 UTC by Mark Wielaard
Modified: 2007-11-29 10:35 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2007-11-29 10:35:19 UTC
$ ./TestRunner -arch 32 frysk.proc.live.TestByteBuffer.testMemoryBufferCapacity

1)
testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError:
Memory Buffer Capacity:  expected:<4294967295> but was:<-1>
   at frysk.proc.live.TestByteBuffer.testMemoryBufferCapacity(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArch32Cases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)


Caused by this piece of code in frysk-sys/frysk/sys/cni/Ptrace.cxx:

jlong
frysk::sys::Ptrace$AddressSpace::length ()
{
  return -1UL;
}

Which is correct for 32 bit systems when frysk is compiled on a 32 bit system
and correct for 64 bit systems when compiled on 64 bit systems. But not for an
32 bit address space on a 64 bit system.