-
Bug
-
Resolution: Fixed
-
P4
-
1.3.0
-
rc1
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2033443 | 1.4.0 | Mandy Chung | P4 | Closed | Fixed | beta |
Name: dkR10031 Date: 04/14/2000
The HotSpot VM 1.3rc3-Z (both win32 and Solaris) fails the test
nsk/jvmdi/SetEventNotificationMode/setnotif001
from testbase_nsk. JVMDI function SetEventNotificationMode ignores it's
third parameter thread: when events are enabled for a particular thread
but this thread is not even started the events are sent nonetheless.
The test below checks only THREAD_START and EXCEPTION_CATCH events but
the same is observed also for other events.
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>
Running on Solaris the test outputs:
$ doit.sh /export/ld24/java/hotspot/jdk1.3.0/solaris
java version "1.3.0rc3"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc3-Z)
Java HotSpot(TM) Client VM (build 1.3.0rc3-Z, interpreted mode)
Event sent from the wrong thread: 6
Event sent from the wrong thread: 6
Event sent from the wrong thread: 30
======================================================================
- backported by
-
JDK-2033443 SetEventNotificationMode ignores its parameter thread
-
- Closed
-
- relates to
-
JDK-4199395 JVMDI: SetEventNotificationMode does not work before thread start event
-
- Closed
-
-
JDK-4419674 JVMDI spec: needs update - new error returned by SetEventNotificationMode
-
- Closed
-