This issue relates to JDK-8043571 (in which changes are made to avoid the assert in JVMTI due to JVMTI's notion of the number of stack frames not matching the actual number of stack frames. This was because of method exit events not being sent for compiled native wrapper frames). JDK-8043571 has changes done to send the method exit events for these wrappers and to thus correct JVMTI's bookkeeping. It also has changes to avoid reading in the return value from the location corresponding to the interpreter generated native stub, since that would be invalid for the compiler generated native wrapper. This issue is raised to enable reading in the native return value from the correct location corresponding to the compiler generated wrapper.
- relates to
-
JDK-8187289 NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled
- Resolved
-
JDK-8041934 com/sun/jdi/RepStep.java fails in RT_Baseline on all platforms with assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync
- Closed
-
JDK-8043571 [REDO] JDK-8041934 com/sun/jdi/RepStep.java fails in RT_Baseline on all platforms with assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync
- Open