public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/49314] md5test, shatest output FAILs on Tru64 UNIX Date: Thu, 16 Jun 2011 17:01:00 -0000 [thread overview] Message-ID: <bug-49314-8172-d8OWTzFch8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49314-8172@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49314 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aph at gcc dot gnu.org, | |tromey at gcc dot gnu.org Target Milestone|--- |4.7.0 --- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> 2011-06-16 16:59:31 UTC --- After some further debugging, I could reproduce the issue with the following testcase: class arraycopy { public static void main(String[] argv) { String src = "a"; byte dst[] = new byte[64]; System.arraycopy (src.getBytes(), 0, dst, 0, src.length()); } } With some debug code in java/lang/natSystem.cc (java::lang::System::arraycopy), I get arraycopy: src_offset = 0 src_a->length = 0 dst_offset = 0 dst_a->length = 64 count = 1 Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Unknown Source) at arraycopy.main(Unknown Source) I haven't yet found where src_a->length is supposed to be initialized. Any suggestions? Rainer
next prev parent reply other threads:[~2011-06-16 17:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-07 17:28 [Bug libgcj/49314] New: " ro at gcc dot gnu.org 2011-06-16 17:01 ` ro at gcc dot gnu.org [this message] 2011-06-16 17:45 ` [Bug libgcj/49314] " tromey at gcc dot gnu.org 2011-06-16 18:20 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-16 18:58 ` tromey at gcc dot gnu.org 2011-06-16 20:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 13:04 ` dominiq at lps dot ens.fr 2011-06-17 13:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 14:04 ` howarth at nitro dot med.uc.edu 2011-06-17 14:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-17 16:17 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-18 5:56 ` howarth at nitro dot med.uc.edu 2011-06-20 14:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-21 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-21 13:59 ` ro at gcc dot gnu.org 2011-06-21 17:11 ` ro at gcc dot gnu.org 2011-06-21 17:13 ` ro at gcc dot gnu.org
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=bug-49314-8172-d8OWTzFch8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.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).