public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/5432] New: testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError: Memory Buffer Capacity: expected:<4294967295> but was:<-1> Date: Thu, 29 Nov 2007 10:35:00 -0000 [thread overview] Message-ID: <20071129103518.5432.mark@klomp.org> (raw) $ ./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.
reply other threads:[~2007-11-29 10:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20071129103518.5432.mark@klomp.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).