8371749: New test serviceability/jvmti/events/VMDeath/AllocatingInVMDeath/TestAllocatingInVMDeath.java fails with -Xcheck:jni

[lmesnik]

Please review following fix that adds jni exception check after calling java code.

Tested by running test with and without -Xcheck:jni.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8371749: New test serviceability/jvmti/events/VMDeath/AllocatingInVMDeath/TestAllocatingInVMDeath.java fails with -Xcheck:jni (Bug - P4)

Reviewers

• Serguei Spitsyn (@sspitsyn - Reviewer)
• Alex Menkov (@alexmenkov - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28280/head:pull/28280
$ git checkout pull/28280

Update a local copy of the PR:
$ git checkout pull/28280
$ git pull https://git.openjdk.org/jdk.git pull/28280/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28280

View PR using the GUI difftool:
$ git pr show -t 28280

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28280.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@lmesnik This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8371749: New test serviceability/jvmti/events/VMDeath/AllocatingInVMDeath/TestAllocatingInVMDeath.java fails with -Xcheck:jni

Reviewed-by: sspitsyn, amenkov

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 18 new commits pushed to the master branch:

• db3a838: 8371436: (fs) java/nio/file/FileStore/Basic.java fails on macOS platform due to assertTrue(!store.equals(prev));
• d09a8cb: 8371746: Some imports in Integer.java and Long.java became unused after JDK-8370503
• 2199b5f: 8371381: [Shenandoah] Setting ergo flags should use FLAG_SET_ERGO
• ... and 15 more: https://git.openjdk.org/jdk/compare/676e6fd8d5152f4e0d14ae59ddd7aa0a7127ea58...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@lmesnik The following label will be automatically applied to this pull request:

• serviceability

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 01: Full - Incremental (12828417)
• 00: Full (8d539f86)

[sspitsyn]

Looks good.

[sspitsyn]

Nit: Typo: s/occured/occurred/
Also, this message is confusing. Unexpected exception occurred in Java upcall made from the cbVMDeath.
Maybe something like this: "cbVMDeath: unexpected exception occurred in Java upcall method".