Integrated: 8335836: serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java fails with unexpected exit code: 112
Serguei Spitsyn
sspitsyn at openjdk.org
Mon Aug 5 23:32:36 UTC 2024
On Tue, 30 Jul 2024 23:13:23 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
This pull request has now been integrated.
Changeset: 965d6b9c
Author: Serguei Spitsyn <sspitsyn at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/965d6b9cbe2dd882fe3c3c955dfa08685af7d6c2
Stats: 42 lines in 1 file changed: 38 ins; 1 del; 3 mod
8335836: serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java fails with unexpected exit code: 112
Reviewed-by: cjplummer, amenkov
-------------
PR: https://git.openjdk.org/jdk/pull/20397
More information about the serviceability-dev
mailing list