On Tue, 15 Jul 2025 07:57:53 GMT, Leonid Mesnik <lmes...@openjdk.org> wrote:
>> The problem happens if post_early_vm_start is triggered. >> The fix is to complete initialization once threadObj become available. >> >> I'vent observed that recompute_enable and hitting assertion might happens >> before this step. However it might be makes sense to check state in >> assertion if needed. > > Leonid Mesnik has updated the pull request incrementally with one additional > commit since the last revision: > > simplified the update test/hotspot/jtreg/serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java line 32: > 30: * @run main/othervm/native -agentlib:AllowedFunctions AllowedFunctions > 31: * @run main/othervm/native -agentlib:AllowedFunctions=with_early_vmstart > AllowedFunctions > 32: * @run main/othervm/native -agentlib:AllowedFunctions=with_early_vmstart > -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n > AllowedFunctions Do I understand correctly this test case reproduces the issue? - there is extra space before `-Xrunjdwp` - would be better to use automatic port (address=0) to avoid "port in use" - need to update (c) years in the file ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/26303#discussion_r2208336956
