RFR: 8335836: serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java fails with unexpected exit code: 112 [v2]

Serguei Spitsyn sspitsyn at openjdk.org
Fri Aug 2 20:34:01 UTC 2024


> 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 two additional commits since the last revision:

 - fix typo in a comment
 - corrections in test ClassPrepare event handler

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/20397/files
  - new: https://git.openjdk.org/jdk/pull/20397/files/f4972661..1671dab0

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=20397&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=20397&range=00-01

  Stats: 8 lines in 1 file changed: 3 ins; 1 del; 4 mod
  Patch: https://git.openjdk.org/jdk/pull/20397.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/20397/head:pull/20397

PR: https://git.openjdk.org/jdk/pull/20397


More information about the serviceability-dev mailing list