On Tue, 21 Jun 2022 08:13:29 GMT, Alan Bateman wrote:
> One thing that I'm wondering for the test is whether to move it to
> test/hotspot/jtreg/runtime/jni/ so it lives with the other tests for JNI. I
> had expected to find other tests for AttachCurrentThread in that location but
> we don't.
On Thu, 16 Jun 2022 13:34:18 GMT, Alan Bateman wrote:
> If several native threads attach to the VM at around the same time, and
> before any threads get an automatically generated name are created, then the
> VM may crash attempting to access the thread status. The issue exists for
> native th
On Tue, 21 Jun 2022 07:09:50 GMT, David Holmes wrote:
> And I confirmed that the VM code will correctly handle a null name from the
> current Java thread.
Thanks, I checked that one.
One thing that I'm wondering for the test is whether to move it to
test/hotspot/jtreg/runtime/jni/ so it lives
On Thu, 16 Jun 2022 13:34:18 GMT, Alan Bateman wrote:
> If several native threads attach to the VM at around the same time, and
> before any threads get an automatically generated name are created, then the
> VM may crash attempting to access the thread status. The issue exists for
> native th
If several native threads attach to the VM at around the same time, and before
any threads get an automatically generated name are created, then the VM may
crash attempting to access the thread status. The issue exists for native
threads that attach explicitly with JNI AttachCurrentThread withou
