RFR: 8309399: JVMTI spec needs to clarify when OPAQUE_FRAME is thrown for reasons other than a native method

[Alan Bateman]

On Thu, 3 Jul 2025 06:05:26 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

> It was decided in a local discussion with Chris and Alan to update the JVMTI spec to make descriptions/clarifications of some `JVMTI_ERROR_OPAQUE_FRAME` cases more consistent.
> This impacts the following JVMTI functions:
>   - `PopFrame`
>   - `NotifyFramePop`
>   - `ForceEarlyReturn<Type>`
> 
> A related CSR is going to be filed for this spec update.
> 
> Testing:
>  - it is N/A in general but mach5 tiers 1-3 will be run to be completely safe

src/hotspot/share/prims/jvmti.xml line 3082:

> 3080:         <error id="JVMTI_ERROR_OPAQUE_FRAME">
> 3081:           The implementation is unable to provide this functionality on this frame
> 3082:           (e.g. the frame at <code>depth</code> is executing a native method).

It might be better to say "unable to generate a FramePop event for the frame" rather than "unable to provide this functionality on this frame".

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/26111#discussion_r2182246125