From: Mark Wielaard <mark@klomp.org>
To: pearly.zhao@oracle.com
Cc: Andrew Cagney <cagney@redhat.com>, frysk@sourceware.org
Subject: Re: [SCM] master: Add a test testMemoryBufferCapacity() to TestByteBuffer.java
Date: Thu, 29 Nov 2007 10:37:00 -0000 [thread overview]
Message-ID: <1196332579.27594.8.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1196238270.19305.2.camel@linux-pzhao.site>
Hi Pearly,
On Wed, 2007-11-28 at 16:24 +0800, Zhao Shujing wrote:
> It's been updated and the test is passing now.
Congrats, it does PASS on x86 and x86_64. And more congrats, since you
seem to have caught a bug on 32bit-on-64bit systems! If you run the test
on a x86_64 system with ./TestRunner -arch 32
frysk.proc.live.TestByteBuffer.testMemoryBufferCapacity you get:
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.
Unfortunately I don't immediately know the correct way to fix this at
this point. So I filed it as
http://sourceware.org/bugzilla/show_bug.cgi?id=5432
If someone knows how to fix this properly you now have a testcase!
Cheers,
Mark
next prev parent reply other threads:[~2007-11-29 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071122090733.7335.qmail@sourceware.org>
2007-11-22 17:10 ` Andrew Cagney
2007-11-23 4:10 ` Zhao Shujing
2007-11-24 0:07 ` Andrew Cagney
2007-11-26 2:53 ` Zhao Shujing
2007-11-27 14:45 ` Andrew Cagney
2007-11-28 8:21 ` Zhao Shujing
2007-11-29 10:37 ` Mark Wielaard [this message]
2007-11-29 10:44 ` Mark Wielaard
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=1196332579.27594.8.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=pearly.zhao@oracle.com \
/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: link
Be 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).