The JDWP spec for StackFrame.SetValue currently states:
"If the thread is a virtual thread then this command can be used to set "
"the value of local variables in the top-most frame when the thread is "
"suspended at a breakpoint or single step event. The target VM may support "
"setting local variables in other cases."
The JDI spec for StackFrame.setValue() has similar wording. InJDK-8308814 the JVMTI spec clarified support to be for a thread suspended at any event, not just a breakpoint or single step. That same clarification is needed in the JDWP and JDI specs. No implementation changes are needed.
"If the thread is a virtual thread then this command can be used to set "
"the value of local variables in the top-most frame when the thread is "
"suspended at a breakpoint or single step event. The target VM may support "
"setting local variables in other cases."
The JDI spec for StackFrame.setValue() has similar wording. In
- csr for
-
JDK-8309149 extend JDI StackFrame.setValue() and JDWP StackFrame.setValues minimal support for virtual threads
-
- Closed
-
- relates to
-
JDK-8308814 extend SetLocalXXX minimal support for virtual threads
-
- Resolved
-
