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

[Chris Plummer]

On Thu, 3 Jul 2025 18:43:19 GMT, Chris Plummer <cjplummer 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 3191:
> 
>> 3189:       <errors>
>> 3190:         <error id="JVMTI_ERROR_OPAQUE_FRAME">
>> 3191:           The implementation is unable to force current frame to return
> 
> Suggestion:
> 
>           The implementation is unable to force the current frame to return

Note this error repeats a few times below. I only tagged this one.

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

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