Name: dkC59003 Date: 04/03/2000



The HotSpot VM 1.3rc2-Y (both win32 and Solaris) fails tests
nsk/jvmdi/ClearFieldAccessWatch/clrfldw001
nsk/jvmdi/ClearFieldAccessWatch/clrfldw002
nsk/jvmdi/ClearFieldModificationWatch/clrfmodw001
nsk/jvmdi/ClearFieldModificationWatch/clrfmodw002
nsk/jvmdi/GetCurrentContendedMonitor/contmon001
nsk/jvmdi/GetCurrentContendedMonitor/contmon002
nsk/jvmdi/GetOwnedMonitorInfo/ownmoninf001
nsk/jvmdi/GetOwnedMonitorInfo/ownmoninf002
nsk/jvmdi/SetEventNotificationMode/setnotif001
nsk/jvmdi/SetFieldAccessWatch/setfldw001
nsk/jvmdi/SetFieldAccessWatch/setfldw002
nsk/jvmdi/SetFieldModificationWatch/setfmodw001
nsk/jvmdi/SetFieldModificationWatch/setfmodw002
from testbase_nsk because the following JVMDI functions return
JVMDI_ERROR_NOT_IMPLEMENTED error code:
ClearFieldAccessWatch
ClearFieldModificationWatch
GetCurrentContendedMonitor
GetOwnedMonitorInfo
SetFieldAccessWatch
SetFieldModificationWatch

To reproduce the bug run
doit.sh <jdk root directory>
or
doit.bat <jdk root directory>
in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>

Classic passes the test (doit.sh <jdk root directory> -classic).

Running on Solaris the test outputs:

$ doit.sh /export/ld24/java/hotspot/jdk1.3.0/solaris
java version "1.3.0rc2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc2-Y)
Java HotSpot(TM) Client VM (build 1.3.0rc2-Y, interpreted mode)
Failed to get owned monitors. err = 99
Failed to get current contended monitor. err = 99
Failed to set field access watch. err = 99
Failed to clear field access watch. err = 99
Failed to set field access watch. err = 99
Failed to clear field access watch. err = 99

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

Name: rmT116609 Date: 08/07/2001


java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)


I've only recently started using an interactive debugger (BugSeeker2 from
www.karmira.com) but have found it interesting to see the different views that
different VMs provide under JPDA.

In particular, I note that HotSpot under both 1.3 and 1.4 doesn't provide
thread monitor status, which can be very useful when investigating deadlocks.
For programs that can run under 1.3, that's not *too* bad, as running under 1.3
provides the information (although then information on thrown exceptions
becomes harder to see).

Under 1.4, however, the Classic VM isn't provided, so there's no way of finding
out which thread holds a monitor for a 1.4-only program.

If JPDA is the future of debugging (and with debuggers like Karmira's I think
it probably will be) this is a great shame.
(Review ID: 129080)
======================================================================