On Fri, 12 May 2023 07:16:57 GMT, Alan Bateman <al...@openjdk.org> wrote:
>> Ok, but JVMTI doesn't use the wording you suggest, and it seems it is in the >> same situation. >> >> >> <error id="JVMTI_ERROR_OPAQUE_FRAME"> >> The thread is a suspended virtual thread and the implementation >> was unable >> to throw an asynchronous exception from the current frame. > >> Ok, but JVMTI doesn't use the wording you suggest, and it seems it is in the >> same situation. > > I don't disagree, it's just a bit more pronounced with JDI because the caller > is in different VM. It's the "current frame" of the Thread in the target VM > rather than the current VM. I'll leave it to you as to whether you want to > re-visit this wording or not. I've updated the text. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/13548#discussion_r1192636454
