JDK-8154989 : For JVMTI method exits from native wrapper frames, read in the native results from the correct location
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • CPU: generic
  • Submitted: 2016-04-25
  • Updated: 2022-10-14
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
tbdUnresolved
Related Reports
Relates :  
JDK-8187289 - NotifyFramePop request is not cleared if JVMTI_EVENT_FRAME_POP is disabled
Relates :  
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
Relates :  
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
Description
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.
Comments
Targeted to tbd as this issue is related to JDK-8043571 which is targeted to tbd.
14-10-2022
Targeted this to 20. At least, this needs to be evaluated. But first, a test is needed to show this problem exists.
03-08-2022
Assigned for evaluation in JDK 14
21-06-2019