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

[Chris Plummer]

On Mon, 7 Jul 2025 17:53:07 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

>>> Then should we say this way: "unable to set a `FramePop` event for the frame" ?
>> 
>> The can_generate_frame_pop_events capability uses "Can set .." so I think what you propose is good. Also the temptation may be to use the word "enable" where but that risks getting confused with enabling events.
>
> Right, thanks! Fixed now.

I don't think this sounds right. You don't "set" a FramePop event. You tell JVMTI to generate a FramePop event when this frame is popped. Maybe something like "A FramePop event cannot be generated for this frame".

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

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