Threads that are popped via JDI/JDWP are typically sitting on
events that have them suspended in the back-end - they are on
RawMonitors. RawMonitorWait fails with the current implementation
(which uses faux exceptions). But even if this could be fixed
the fact that the exception is exposed will cause many other
falures. Re-implement with another mechanism.
Name: elR10090 Date: 08/28/2001
This bug affects the following test from testbase_nsk:
nsk/jvmdi/PopFrame/popframe004
Pavel N. Visotsky, ###@###.###
======================================================================
events that have them suspended in the back-end - they are on
RawMonitors. RawMonitorWait fails with the current implementation
(which uses faux exceptions). But even if this could be fixed
the fact that the exception is exposed will cause many other
falures. Re-implement with another mechanism.
Name: elR10090 Date: 08/28/2001
This bug affects the following test from testbase_nsk:
nsk/jvmdi/PopFrame/popframe004
Pavel N. Visotsky, ###@###.###
======================================================================
- duplicates
-
JDK-4434422 HS1.4 crashes with assertion at resourceArea.hpp, 48
-
- Closed
-
-
JDK-4414286 VM crashes while executing resumed thread after popping a frame
-
- Closed
-