JDK-4407397 : JDI: incorrect notification of caught and uncaught exception events
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.3.1,1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2001-01-23
  • Updated: 2002-08-30
  • Resolved: 2002-08-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other
1.3.1 ladybirdFixed 1.4.0Fixed
Related Reports
Relates :  
JDK-4696594 - REGRESSION:JDI: incorrect notification of caught and uncaught exception events
Relates :  
JDK-4627997 - JDI testcase crexreq001 failing with -client -Xcomp only, all platforms
Relates :  
JDK-4397764 - JDI: Uncaught exception in debugee does not lead to VM exit
Relates :  
JDK-4323439 - EventRequestManager.createExceptionRequest() does not behave as expected
Description

Name: elR10090			Date: 01/23/2001


 The HotSpot VM (from both ladybird and merlin) fails to pass the tests

nsk/jdi/EventRequestManager/createExceptionRequest/crexreq001,
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq006,
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq008

from testbase_nsk on all platforms.

 The tests consist of debugger part (crexreq00X.java) and debugee part
(crexreq00Xt.java). The debugger creates requests of the exception events
in debugee using
com.sun.jdi.request.EventRequestManager.createExceptionRequest()
with various combinations of booolean notifyCaught and notifyUncaught
parameters.
The debugee incorrectly notifies or does not notify the debugger about 
caught and uncaught exception events. 
 
JDK version
-----------
java version "1.3.1beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1beta-b13)
Java HotSpot(TM) Client VM (build 1.3.1beta-b13, mixed mode)

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

Platforms
---------
Solaris sparc 5.7, Linux Red Hat 6.2, Windows NT 4.0 

Error message from output of the test execution
-----------------------------------------------
# ERROR: TEST FAILED: test case #3: caught exception
java.lang.NumberFormatException was reported by the debugger
# ERROR: TEST FAILED: test case #4: caught exception
nsk.jdi.EventRequestManager.createExceptionRequest.crexreq001tException was not
reported by the debugger

Test source files location
--------------------------
/net/sqesvr/export/vsn/GammaBase/Bugs/<this bug number>

Scripts to reproduce the failure
--------------------------------
/net/sqesvr/export/vsn/GammaBase/Bugs/<this bug number>/crexreq001/doit.ksh
<JAVA_HOME>
/net/sqesvr/export/vsn/GammaBase/Bugs/<this bug number>/crexreq006/doit.ksh
<JAVA_HOME>
/net/sqesvr/export/vsn/GammaBase/Bugs/<this bug number>/crexreq008/doit.ksh
<JAVA_HOME>

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

Name: egR10015			Date: 02/04/2001


This bug also affects the following tests from testbase_nsk:
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq002
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq003
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq004
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq005
nsk/jdi/EventRequestManager/createExceptionRequest/crexreq007

======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: ladybird merlin-beta FIXED IN: ladybird merlin-beta INTEGRATED IN: ladybird merlin-beta VERIFIED IN: ladybird-rc1 merlin-rc1
14-06-2004
EVALUATION Begin - robert.field@Eng 2001-01-31 The JDI front-end EventRequestManagerImpl did not send a filter to the back-end if both caught and uncaught were set to false. Fix ready for review. End - robert.field@Eng 2001-01-31
31-01-2001