8346717: serviceability/dcmd/vm/SystemDumpMapTest.java failing on Windows with "Stack base not yet set for thread id"

[stooke]

This test fixes an issue with incomplete Windows threads not yet having a stack. A test for a null stack_base is added to guard against the potential null dereference. An additional test using ZGC is added to the jtreg SystemMapTest.

---

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-8346717: serviceability/dcmd/vm/SystemDumpMapTest.java failing on Windows with "Stack base not yet set for thread id" (Bug - P3)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22870

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back stooke! 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 change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@stooke To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels

• build
• client
• compiler
• core-libs
• graal
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah

[stooke]

/label jcmd

[openjdk]

@stooke
The label jcmd is not a valid label.
These labels are valid:

• graal
• serviceability
• hotspot
• hotspot-compiler
• ide-support
• kulla
• i18n
• shenandoah
• jdk
• javadoc
• security
• hotspot-runtime
• jmx
• build
• nio
• client
• core-libs
• compiler
• net
• hotspot-gc
• hotspot-jfr

[stooke]

/label hotspot serviceability

[openjdk]

@stooke
The hotspot label was successfully added.

The serviceability label was successfully added.

[openjdk]

⚠️ @stooke This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

[mlbridge]

Webrevs

• 00: Full (1da4240d)

[lmesnik]

No need to add separate testcase for ZGC. It is expected that hotspot tests are usually executed to ensure that all functionality works with any GC.
If you want to add it to ensure that regression testcase is always executed even no ZGC is set then please

1. add
   * @requires vm.gc.Z
   So testcase is not executed if non-ZGC GC (Parallel/Serial etc) is set explicitly.
2. Add
   * @bug 8346717
3. Add id like
   * @test id=zgc
   to make testcase name clearer.