On Tue, 30 May 2023 23:44:28 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> 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. In > [JDK-8308814](https://bugs.openjdk.org/browse/JDK-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. This pull request has now been integrated. Changeset: e8271649 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/e8271649e00771a8bbee240aa1bbbc27a672b22a Stats: 5 lines in 2 files changed: 0 ins; 0 del; 5 mod 8309146: extend JDI StackFrame.setValue() and JDWP StackFrame.setValues minimal support for virtual threads Reviewed-by: sspitsyn, alanb ------------- PR: https://git.openjdk.org/jdk/pull/14235
