Integrated: 8301798: [BACKOUT] jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of SUSPEND_ALL

Fri Feb 3 22:25:59 UTC 2023

On Fri, 3 Feb 2023 18:56:39 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

> Backing out the following due to numerous failing tests. There will be no redo. The original change was an enhancement, not a bug fix.
> 
> [JDK-8300811](https://bugs.openjdk.org/browse/JDK-8300811) jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of SUSPEND_ALL
> 
> Tested with 100 runs of com/sun/jdi on macosx-x64 (product build) which is where almost all of the failures were reported. Also did a full tier3 mach5 run.

This pull request has now been integrated.

Changeset: 3be5317b
Author:    Chris Plummer <cjplummer at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/3be5317b592f1bda76aea5fbcbb98c6fa633401c
Stats:     4 lines in 1 file changed: 0 ins; 3 del; 1 mod

8301798: [BACKOUT] jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of SUSPEND_ALL

Reviewed-by: dcubed, dholmes

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

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