JDK-8319875 : Add macOS implementation for jcmd System.map
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • Submitted: 2023-11-10
  • Updated: 2025-10-24
  • Resolved: 2024-12-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25 b03Fixed
Related Reports
Relates :  
JDK-8318636 - Add jcmd to print annotated process memory map
Relates :  
JDK-8370578 - SystemMapTest.java#normal fails intermittendly on macOS aarch64
Description
Add a MacOs implementation for this command. If all else fails, based on parsing the output of vmmap.
Comments
Yes, please open a new issue, and please provide more information (macOS version, command line would be helpful, for example).
24-10-2025
I created JDK-8370578 .
24-10-2025
Hi Simon [~stooke], we had the test serviceability/dcmd/vm/SystemMapTest.java#normal failing today on macOS aarch64 : In the log we find : 0x000102cec000-0x000102cf4000 32768 rw-/rwx shr 0 INTERN /private/var/folders/ps/6ym_x8gd6qz72g9288px78pc0003kp/T/hsperfdata_jvmtests/28134 but the regex is : java.lang.RuntimeException: '0x\\p{XDigit}+-0x\\p{XDigit}+ +\\d+ +[\\-rwx]*/[\\-rwx]* +pvt +(0x\\p{XDigit}+|\\d+) +.*/.*/hsperfdata_.*' missing from stdout/stderr at jdk.test.lib.process.OutputAnalyzer.shouldMatch(OutputAnalyzer.java:372) at SystemMapTest.run(SystemMapTest.java:67) at SystemMapTest.jmx(SystemMapTest.java:78) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) at java.base/java.lang.reflect.Method.invoke(Method.java:565) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132) at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599) at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174) at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46) at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822) at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128) at java.base/java.util.ArrayList.forEach(ArrayList.java:1604) Seems the test expects "pvt" but gets "shr" in the output - any idea? Should we handle "shr" too in the test ? Should I open a separate issue for this?
24-10-2025
Changeset: 3b9de117 Branch: master Author: Simon Tooke <stooke@openjdk.org> Committer: Thomas Stuefe <stuefe@openjdk.org> Date: 2024-12-14 06:13:26 +0000 URL: https://git.openjdk.org/jdk/commit/3b9de117e83a7875df7fd2ddcc9d896f027e2c92
14-12-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/20953 Date: 2024-09-11 18:22:00 +0000
24-10-2024
Runtime Triage: This is not on our current list of priorities. We will consider this feature if we receive additional customer requirements.
12-07-2024