-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
1.3.0
-
sparc
-
solaris_7
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, compiled 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.
Then the test requests and analyses the MONITOR_DUMP event info for this state.
When the test runs under the HotSpot in the compiled mode
the RequestEvent for JVMPI_EVENT_MONITOR_DUMP crashes
the HotSpot VM.
In the mixed and interpreted modes this failure does not happen
but the other bug is revealed (see the field - See also:).
To reproduce the bug run doit.sh on Solaris in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>:
doit.sh <JDK root directory> -Xcomp
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. -Xcomp for the current case).
See logs:
% doit.sh /net/java7/d/bond/java/dest/Solaris_JDK_1.3-b09 -Xcomp
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, compiled 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!
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: post JVMPI monitor dump
#
# Error ID: 4E4D4554484F440E4350500162 01
#
# Problematic Thread: prio=5 tid=0x95ca8 nid=0x4 runnable
#
(Error ID: nmethod.cpp, 354)
======================================================================
- duplicates
-
JDK-4418568 NULL thread ID in MONITOR_DUMP
- Resolved
- relates to
-
JDK-4387957 Thread dump under hotspot does not indicate monitor ownership
- Closed
-
JDK-4329157 MONITOR_DUMP event info contains incorrect items
- Closed