8258404: Restore stacktrace reuse after 8258094

[mgronlun]

Greetings,

a tiny adjustment to restore the possibility of capitalizing on a cached stacktrace.

Thanks
Markus

---

Progress

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

Issue

• JDK-8258404: Restore stacktrace reuse after 8258094

Reviewers

• Erik Gahlin (@egahlin - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk16 pull/23/head:pull/23
$ git checkout pull/23

[bridgekeeper]

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

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

• hotspot-jfr

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

• 00: Full (766fa55)

[openjdk]

@mgronlun 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:

8258404: Restore stacktrace reuse after 8258094

Reviewed-by: egahlin

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 2 new commits pushed to the master branch:

• 7ff9c85: 8258242: Type profile pollution occurs when memory segments of different kinds are used
• 09e8675: 8255381: com/sun/jdi/EATests.java should not suspend graal threads

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.

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

[mgronlun]

/integrate

[openjdk]

@mgronlun Since your change was applied there have been 2 commits pushed to the master branch:

• 7ff9c85: 8258242: Type profile pollution occurs when memory segments of different kinds are used
• 09e8675: 8255381: com/sun/jdi/EATests.java should not suspend graal threads

Your commit was automatically rebased without conflicts.

Pushed as commit fa1cbb4.

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