RFR: 8348203: [JVMCI] Make eager JVMCI initialization observable in the debugger

[Volker Simonis]

On Wed, 22 Jan 2025 00:25:56 GMT, David Holmes <dholmes at openjdk.org> wrote:

> It is not at all obvious what other impacts moving this could have. Is it really appropriate to enter the live phase and claim the VM is initialized if we may error out if JVMCI initialization fails after that point.
> 

Yes, because that's the normal case. Usually, JVMCI gets initialized lazily, before its first usage which is much after VMInit was posted. We are looking at a special case here because this patch only moves **eager** JVMCI initialization (which happens with `-XX:+EagerJVMCI`, `-XX:+JVMCIPrintProperties` and `-XX:+JVMCILibDumpJNIConfig`) after the VMInit event was posted.

> What prevents you from doing the debugging you want to do? 

Very simple - the debugger is not starting before it gets the VMInit event.
 
> And why are you "debugging" Graal compiler initialization anyway?

Is this a serious question? Because I'm hunting a bug in eager JVMCI initialization.

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

PR Comment: https://git.openjdk.org/jdk/pull/23219#issuecomment-2607443519