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

Serguei Spitsyn sspitsyn at openjdk.org
Mon Jul 7 17:55:40 UTC 2025


On Fri, 4 Jul 2025 06:15:43 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> Good suggestion, thanks.
>> `NotifyFramePop` does not generate the `FramePop` events by itself it is just sets or enables events.
>> Then should we say this way: "unable to set a `FramePop` event for the frame" ?
>
>> 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!

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

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


More information about the serviceability-dev mailing list