JDK-7200092 : Make NMT a bit friendlier to work with
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-09-21
  • Updated: 2013-06-26
  • Resolved: 2012-10-02
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 7 JDK 8 Other
7u40Fixed 8Fixed hs24Fixed
Related Reports
Relates :  
I was trying out NMT a few days ago but couldn't get it to work until I realised I gave it the wrong option, and it swallowed it silently but didn't do anything.
I was trying to use -XX:NativeMemoryTracking=details instead of -XX:NativeMemoryTracking=detail because because of a typo in a pdf.

It would be much friendlier if we failed explicitly and printed out the offending option given.

Verified with jdk8-b60 on Windows 7 x64.

EVALUATION Fix is to exit on encountering a bad option, and printing the name of that option.