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

[Serguei Spitsyn]

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 spec sections:
>   - `PopFrame`
>   - `NotifyFramePop`
>   - `ForceEarlyReturn<Type>`
>   - `GetLocal<Type>`
>   - `SetLocal<Type>`
>   - general description of the `JVMTI_ERROR_OPAQUE_FRAME` error code
>   
> 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

This pull request has now been integrated.

Changeset: a65d9532
Author:    Serguei Spitsyn <sspitsyn at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/a65d9532ed454a0f70b1009181a25b23a38ccd4b
Stats:     85 lines in 1 file changed: 5 ins; 48 del; 32 mod

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

Reviewed-by: cjplummer

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

PR: https://git.openjdk.org/jdk/pull/26111