8292695: SIGQUIT and jcmd attaching mechanism does not work with signal chaining library

[caoman]

Backport of https://bugs.openjdk.org/browse/JDK-8292695

---

Progress

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

Issue

• JDK-8292695: SIGQUIT and jcmd attaching mechanism does not work with signal chaining library

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 59

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19u/pull/59.diff

[bridgekeeper]

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

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

8292695: SIGQUIT and jcmd attaching mechanism does not work with signal chaining library

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:

• 25448dc: 8292899: CustomTzIDCheckDST.java testcase failed on AIX platform

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 (115b9546)

[caoman]

/integrate

[openjdk]

@caoman
Your change (at version 115b954) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

[openjdk]

Going to push as commit 41677c1.
Since your change was applied there has been 1 commit pushed to the master branch:

• 25448dc: 8292899: CustomTzIDCheckDST.java testcase failed on AIX platform

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @caoman Pushed as commit 41677c1.

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

[caoman]

Thanks for sponsoring, Paul!