On Tue, 4 Aug 2026 21:04:54 GMT, Chris Plummer <[email protected]> wrote:
>> Yes, jdb does learn about vthreads that arrive in events, and they should be >> returned by the "threads" command until they exit. I did something similar >> with some of the nsk/jdi tests, relying on events to learn about threads. >> >> BTW, there are still some nsk/jdi tests that rely on >> includevirtualthreads=y. They are listed in >> [JDK-8356823](https://bugs.openjdk.org/browse/JDK-8356823) if you are >> interested in fixing them. > > I'm not sure what you are asking w.r.t. threads002. The changes below look > fine. It was adding -trackallthreads that I think is problematic. It's unclear to me why your changes to the test resulted in needing to pass -trackallthreads. You switched from getThreadIds() to getThreadIdsByName(), but both use the set of threads returned by the "threads" command, so I don't see why that change would impact the need for -trackallthreads. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32142#discussion_r3716244277
