JDK-8322811 : jcmd System.dump_map help info has conflicting statements
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-01-02
  • Updated: 2024-06-20
  • Resolved: 2024-06-10
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 24
24 b02Fixed
Related Reports
Relates :  
JDK-8334164 - The fix for JDK-8322811 should use _filename.is_set() rather than strcmp()
Relates :  
JDK-8323546 - Cleanup jcmd docs for Compiler.perfmap and VM.cds filename parameter
Relates :  
JDK-8318636 - Add jcmd to print annotated process memory map
Description
This is the help output:

System.dump_map
Dumps an annotated process memory map to an output file (linux only).

Impact: Low

Syntax : System.dump_map [options]

Options: (options must be specified using the <key> or <key>=<value> syntax)
	-H : [optional] Human readable format (BOOLEAN, false)
	-F : [optional] file path (defaults: "vm_memory_map_<pid>.txt") (STRING, no default value)

The documentation for the -F option states there is both a default and not a default, value. It should read:

-F : [optional] file path (STRING, "vm_memory_map_<pid>.txt")
Comments
Changeset: 83b34410 Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2024-06-10 09:00:05 +0000 URL: https://git.openjdk.org/jdk/commit/83b34410e326c47f357a37c3a337b7dedb8cbbda
10-06-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/19596 Date: 2024-06-07 10:40:07 +0000
10-06-2024