Name: ipR10196 Date: 06/17/2002


--------------------------------------
Test : Xnsk/jvmdi/Allocate/alloc001
TestBase : testbase_nsk
VM : server 64-bit
Mode : int
Platform : Itanium
OS : Redhat Linux 7.2
----------------------------------------

Steps to reproduce
================
1. cd /net/sqesvr.eng/export/vsn/GammaBase/Bugs/{BugID}
2. sh doit.sh $JAVA_HOME

This testcase passed on Windows-ia64 and failed on Linux-ia64.
This testcase checks JVMDI memory allocation features. On the final
"Out of memory check" it tries to allocate all available memory until
JVMDI_ERROR_OUT_OF_MEMORY is received. However, on Linux-ia64 java
process is killed instead:

  >>> Null pointer check ...
  >>> ... done
  >>> Accessibility check ...
  >>> ... done
  >>> Out of memory check ...
  doit.sh: line 115: 20707 Killed $JDK/bin/java$JG $OPT -Xdebug -Xnoagent -Xrun${TEST}:$PAR $TEST
  Exit Code: 137

The following is e-mail message from Bob Vandette about this failure:
--------------------------------------------------------------------
Date: Wed, 12 Jun 2002 12:59:16 -0400
From: Bob Vandette <###@###.###>
To: "Ivan Popov[Contractor]" <###@###.###>
CC: Jim Holmlund <###@###.###>, ###@###.###,
    ###@###.###, ###@###.###
Subject: Re: testcase for JVMDI memory management

According to Steve Goldman who looked at this, this bug is in the Linux
OS. If you allocate all the memory in the system, Linux terminates your
application rather than returning an error to the malloc system call.

This does not affect Java applications, only native JNI code that does it's
own memory allocation.

So if you file a bug, we will probably have to keep it open until the next rev
of the OS.

Bob.
--------------------------------------------------------------------

I've also noticed once that the test hanged up in the final loop
of memory eating on 64-bit Solaris-sparcv9 platform, but I cannot
reproduce this failure anymore.

======================================================================

Name: elR10090 Date: 10/06/2003


The JVMTI variant of the same test also causes the
same problem with Linux/AMD64:

    Xnsk/jvmti/Allocate/alloc001


======================================================================