[Bug libgcj/49314] New: md5test, shatest output FAILs on Tru64 UNIX

["ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

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