RFR: 8335836: serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java fails with unexpected exit code: 112 [v5]
Chris Plummer
cjplummer at openjdk.org
Mon Aug 5 17:31:33 UTC 2024
On Sat, 3 Aug 2024 11:44:02 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:
>> The test has been fixed to:
>> - add a guard against JVMTI_ERROR_WRONG_PHASE
>> - replace `exit(err)` with `abort()` in the `check_jvmti_error()`
>>
>> The JVMTI `VMDeath` event is enabled and a `RawMonitor` is introduced to serialize `ClassPrepare` and `VMDeath` events, and so, to prevent JVMTI_ERROR_WRONG_PHASE in the `ClassPrepare` events.
>>
>> Testing:
>> - run the test AllowedFunctions.java locally
>> - TBD: submit a mach5 run for fixed test
>
> Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision:
>
> minor simplified tweak
Looks good.
-------------
Marked as reviewed by cjplummer (Reviewer).
PR Review: https://git.openjdk.org/jdk/pull/20397#pullrequestreview-2219527246
More information about the serviceability-dev
mailing list