-
Type:
Sub-task
-
Resolution: Delivered
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: core-svc
[StackFrame.SetValues], [StackFrame.GetValues], [ThreadReference.PopFrames], and [ThreadReference.ForceEarlyReturn] all received specification updates to clarify when `OPAQUE_FRAME` and `INVALID_SLOT` errors are returned.
(1) The JDWP specification for `StackFrame.GetValues` did not mention `OPAQUE_FRAME` as a possible error, but it is possible. The specification has been updated to include language regarding when `OPAQUE_FRAME` can be returned.
(2) The JDWP specification for `StackFrame.SetValue` only mentioned `OPAQUE_FRAME` as a possible error for virtual threads, indicating that the operation is not possible on the specified frame. However, `OPAQUE_FRAME` is possible for other reasons, such as the frame being native. The specification has been updated to adopt the more general description of when `OPAQUE_FRAME` can be returned.
(3) The JDWP specification `StackFrame.PopFrames` and `ThreadReference.ForceEarlyReturn` was too specific with regards to when `OPAQUE_FRAME` can be returned. The specification has been updated to adopt the more general description of when `OPAQUE_FRAME` can be returned.
(4) The JDWP specification for `StackFrame.SetValue` failed to mention `INVALID_SLOT` as a possible error result. This has been fixed.
(1) The JDWP specification for `StackFrame.GetValues` did not mention `OPAQUE_FRAME` as a possible error, but it is possible. The specification has been updated to include language regarding when `OPAQUE_FRAME` can be returned.
(2) The JDWP specification for `StackFrame.SetValue` only mentioned `OPAQUE_FRAME` as a possible error for virtual threads, indicating that the operation is not possible on the specified frame. However, `OPAQUE_FRAME` is possible for other reasons, such as the frame being native. The specification has been updated to adopt the more general description of when `OPAQUE_FRAME` can be returned.
(3) The JDWP specification `StackFrame.PopFrames` and `ThreadReference.ForceEarlyReturn` was too specific with regards to when `OPAQUE_FRAME` can be returned. The specification has been updated to adopt the more general description of when `OPAQUE_FRAME` can be returned.
(4) The JDWP specification for `StackFrame.SetValue` failed to mention `INVALID_SLOT` as a possible error result. This has been fixed.