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

[Serguei Spitsyn]

On Thu, 10 Jul 2025 00:15:21 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

>> Chris, please, let me know if it is okay to keep this at is or you still want an update for the `NotifyFramePop`.
>
> I understand what you are saying about the comparison to SetBreakpoint and that SetFramePop would have been a better name, but I don't see what this with the description. I said "set a FramePop event" doesn't sound right. Neither would "set a Breakpoint event". Also, the analogy with breakpoints doesn't really work when you consider that "a breakpoint" is meaningful, but "a FrampPop" does not.
> 
> A breakpoint is a location in the code where a breakpoint event will be triggered when executed. That analogy doesn't really work with FramePop. We don't have a word similar to breakpoint that means "a frame marked for generating a FramePop event when popped".

Okay, thanks. I've updated the `NotifyFramePop` spec as you suggested:
 ```A FramePop event cannot be generated for this frame```

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

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