Name: dkC59003 Date: 04/10/2000


The regression test (testbase_nsk) nsk/regression/b4311308 crashes
the HotSpot Client VM (build product+2.0+baseline+compiler1+20000401-003153, mixed mode)
on Solaris.

The test creates the situation when the thread (One_Thread) is owner
of the java_monitor and is waiting to be notified for the other java_monitor.
When the test analyses the MONITOR_DUMP event info for this state an unexpected
exception happens in native code outside the VM..

The log below shows that this exception is caused by the incorrect
MONITOR_DUMP event info which contains the incorrect items:
 - entry count =16777216
 - number of threads waiting to be notified =16777216


This failure happens in the mixed and interpreted modes.
In the compiled mode the other bug is revealed
(see the field - See also:).

Under the HotSpot) Client VM (build 1.3.0rc3-Z, interpreted mode)
this failure does not happen but the #4311308 bug is revealed.

To reproduce the bug run doit.sh on Solaris in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>:
   doit.sh <JDK root directory>
   doit.sh <JDK root directory> -Xint

The first parameter for doit.sh should be JDK root directory
(e.g. /export/ld/java/jdk1.3/solaris) and the other parameter(s) -
VM option(s) (optional, e.g. -Xint for the current case).



See logs:

novo73% doit.sh /net/java7/d/bond/java/dest/Solaris_JDK_1.3-b09
java version "1.3"
Java(TM) 2 Runtime Environment, Standard Edition (build Solaris_JDK_1.3-b09)
Java HotSpot(TM) Client VM (build product+2.0+baseline+compiler1+20000401-003153, mixed mode)
==> nsk/regression/b4311308 test LOG:
----> Thread - One_Thread(lockA, lockB) - Started!
----> state N 1: b4311308.lockA has been locked by One_Thread
----> One_Thread is waiting for b4311308.barrier notification
====> checking Monitor Dump for state N 1...
----> Request Event For Monitor Dump...
----> native: RequestEventForMonitorDump from b4311308 received!
----> native: Caught JVMPI_EVENT_MONITOR_DUMP: dump_begin = 0x103c78, dump_end = 0x103cd8
----> native: Caught JVMPI_EVENT_MONITOR_DUMP: END!
----> native: RequestEventForMonitorDump from b4311308 made!
----> analysing of Monitor Dump...
----> native: Monitor Number 1 will be analyse...
----> native: monitor Id: 0xf4c308d8
----> native: owner env ID: 0
----> native: entry count =16777216
----> native: number of threads waiting to enter =0
----> native: number of threads waiting to be notified =16777216
#
# An unexpected exception has been detected in native code outside the VM.
# Program counter=0xff2706bc
#
# Problematic Thread: prio=1 tid=0x27ee8 nid=0x1 runnable
#


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