-
Bug
-
Resolution: Won't Fix
-
P4
-
25
For this test the debuggee throws two exceptions, one caught and one uncaught. The debugger expects to receive ExceptionEvents for these two exceptions, which it does. However, it ends up getting two ExceptionEvents for the uncaught exception when run with the virtual thread wrapper. This is because the wrapper adds an exception handler, so the "uncaught" exception ends up being caught and then rethrown, resulting in two ExceptionEvents instead of one.
The test should be verifying that the "uncaught" exception is indeed uncaught, and it should also verify that both of the thrown exceptions are only thrown once. However, currently it will fail if either of these checks are made until the issue with the wrapper's added exception handler is addressed. I believe this can be done by modifying the test to throw the exceptions in a different thread rather than in the main thread. This way there will be no exception handler installed.
The test should be verifying that the "uncaught" exception is indeed uncaught, and it should also verify that both of the thrown exceptions are only thrown once. However, currently it will fail if either of these checks are made until the issue with the wrapper's added exception handler is addressed. I believe this can be done by modifying the test to throw the exceptions in a different thread rather than in the main thread. This way there will be no exception handler installed.
- relates to
-
JDK-8357184 Test vmTestbase/nsk/jdi/ExceptionEvent/_itself_/exevent008/TestDescription.java fails with unreported exception
-
- Resolved
-