8241948: enhance list of environment variables printed in hs_err file

[omikhaltsova]

I'd like to backport JDK-8241948 to jdk13u for parity with jdk11u.
The original patch applied cleanly. Tested via build.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8241948: enhance list of environment variables printed in hs_err file

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk13u-dev pull/180/head:pull/180
$ git checkout pull/180

Update a local copy of the PR:
$ git checkout pull/180
$ git pull https://git.openjdk.java.net/jdk13u-dev pull/180/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 180

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk13u-dev/pull/180.diff

[bridgekeeper]

👋 Welcome back omikhaltcova! 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]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

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

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

8241948: enhance list of environment variables printed in hs_err file

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 1 new commit pushed to the master branch:

• efc81a3: 8264640: CMS ParScanClosure misses a barrier

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (61357a1d)

[omikhaltsova]

/integrate

[openjdk]

@omikhaltsova
Your change (at version 61357a1) is now ready to be sponsored by a Committer.

[yan-too]

/sponsor

[openjdk]

@yan-too @omikhaltsova Since your change was applied there has been 1 commit pushed to the master branch:

• efc81a3: 8264640: CMS ParScanClosure misses a barrier

Your commit was automatically rebased without conflicts.

Pushed as commit 7daf680.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.