[jdk19] RFR: 8287847: Fatal Error when suspending virtual thread after it has terminated [v7]

[Serguei Spitsyn]

On Fri, 1 Jul 2022 18:17:35 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

>> This fixes a bug in the debug agent when there is a request to suspend a virtual thread that has already terminated. The issue was that unless the debug agent was currently under a "suspend all", it would not properly put the virtual thread on the `otherThreads` list, and instead added it to `runningVThreads`. This meant at the end of `insertThread()` the following code tried to do a JVMTI `SetThreadLocalStorage`, which can't be done on a terminated thread.
>> 
>> 
>>         if (list != &otherThreads) {
>>             setThreadLocalStorage(node->thread, (void*)node);
>>         }
>
> Chris Plummer has updated the pull request incrementally with one additional commit since the last revision:
> 
>   provide a slightly more descriptive @summary

test/jdk/com/sun/jdi/SuspendAfterDeath.java line 73:

> 71: 
> 72: public class SuspendAfterDeath extends TestScaffold {
> 73:     private volatile ThreadReference thread;

One minor naming suggestion:
The name `thread` is too generic. What about something like `targetThread` or `testedThread`?

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

PR: https://git.openjdk.org/jdk19/pull/88