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] New: md5test, shatest output FAILs on Tru64 UNIX
Date: Tue, 07 Jun 2011 17:28:00 -0000 [thread overview]
Message-ID: <bug-49314-8172@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49314
Summary: md5test, shatest output FAILs on Tru64 UNIX
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcj
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
Host: alpha-dec-osf5.1b
Target: alpha-dec-osf5.1b
Build: alpha-dec-osf5.1b
Of the 12 remaining libjava failures on Tru64 UNIX, 8 are due to the same
reason:
FAIL: md5test output - source compiled test
FAIL: md5test -findirect-dispatch output - source compiled test
FAIL: md5test -O3 output - source compiled test
FAIL: md5test -O3 -findirect-dispatch output - source compiled test
FAIL: shatest execution - source compiled test
FAIL: shatest -findirect-dispatch execution - source compiled test
FAIL: shatest -O3 execution - source compiled test
FAIL: shatest -O3 -findirect-dispatch execution - source compiled test
Running md5test manually, I get 6 times this output:
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Unknown Source)
at gnu.java.security.hash.BaseHash.update(Unknown Source)
at gnu.java.security.jce.hash.MessageDigestAdapter.engineUpdate(Unknown
Source)
at java.security.DummyMessageDigest.engineUpdate(Unknown Source)
at java.security.MessageDigest.update(Unknown Source)
at md5test.testString(Unknown Source)
at md5test.main(Unknown Source)
Unfortunately, gdb 7.2.50 is no help:
Reading symbols from
/var/gcc/gcc-4.7.0-20110530/5.1b-gcc/alpha-dec-osf5.1b/libjava/testsuite/md5test.exe...done.
(gdb) run
Starting program:
/var/gcc/gcc-4.7.0-20110530/5.1b-gcc/alpha-dec-osf5.1b/libjava/testsuite/md5test.exe
/vol/src/gnu/gdb/gdb-git/gdb/utils.c:1446: internal-error: virtual memory
exhausted: can't allocate 8375 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
next reply other threads:[~2011-06-07 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 17:28 ro at gcc dot gnu.org [this message]
2011-06-16 17:01 ` [Bug libgcj/49314] " ro at gcc dot gnu.org
2011-06-16 17:45 ` 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@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: 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).