This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/5432] New: testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError: Memory Buffer Capacity: expected:<4294967295> but was:<-1>
- From: "mark at klomp dot org" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 29 Nov 2007 10:35:19 -0000
- Subject: [Bug general/5432] New: testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError: Memory Buffer Capacity: expected:<4294967295> but was:<-1>
- Reply-to: sourceware-bugzilla at sourceware dot org
$ ./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.
--
Summary: testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)
junit.framework.AssertionFailedError: Memory Buffer
Capacity: expected:<4294967295> but was:<-1>
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: mark at klomp dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=5432
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.