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

[Serguei Spitsyn]

On Tue, 15 Jul 2025 03:12:13 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

> So if a combination of a native method and invalid slot results in OPAQUE_FRAME, then we need to update the JDWP spec to reflect this.

Agreed

> And speaking of INVALID_SLOT, it missing in the JDWP spec for SetValues, but is there for GetValues. It seems that should be fixed.

Agreed

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

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