RFR: 8282475: SafeFetch should not rely on existence of Thread::current

[Anton Kozlov]

On Sun, 20 Mar 2022 22:49:49 GMT, David Holmes <david.holmes at oracle.com> wrote:

> My comment was specifically in response to your statement:
> > I see AsyncGetCallTrace to assume the JavaThread very soon
> 
> But AGCT is only intended to ever be called on JavaThreads.

Sorry, it was my question. It looked for me this way as well (and that ACGT will return shortly if called on non-Java thread; AFAICS SafeFetch in not involved), and I wanted to confirm. The AGCT on non-Java thread was declared to be one of the two major reasons for this patch.

I would support this patch to move W^X management out from Thread to OS-specific code, after the problem with the assert "is initialized" is fixed.

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

PR: https://git.openjdk.java.net/jdk/pull/7727