ADDITIONAL SYSTEM INFORMATION :
Linux 8f64da1a8018 4.14.77-69.57.amzn1.x86_64 #1 SMP Tue Nov 6 21:32:55 UTC 2018 x86_64 Linux

openjdk version "1.8.0_171"
OpenJDK Runtime Environment (IcedTea 3.8.0) (Alpine 8.171.11-r0)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)

A DESCRIPTION OF THE PROBLEM :
Java argument parser is causing a Segmentation Fault when NMT "detail" flag is enabled and placed before "-version".

Behaviour was observed both in versions 1.8.0_171 and 1.8.0_181.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
/ # java -version -XX:NativeMemoryTracking=summary
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (IcedTea 3.8.0) (Alpine 8.171.11-r0)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
/ #
/ #
/ #
/ # java -version -XX:NativeMemoryTracking=detail
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (IcedTea 3.8.0) (Alpine 8.171.11-r0)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
/ #
/ #
/ # java -XX:NativeMemoryTracking=detail -version
Segmentation fault
/ #
/ # java -XX:NativeMemoryTracking=summary -version
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (IcedTea 3.8.0) (Alpine 8.171.11-r0)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
- Install Alpine Linux on a docker container
- Execute java -version -XX:NativeMemoryTracking=detail
- Get segmentation fault instantly

ACTUAL -
Segmentation Fault error is thrown on JVM start

CUSTOMER SUBMITTED WORKAROUND :
Executing "java -XX:NativeMemoryTracking=detail -version" instead of "java -version -XX:NativeMemoryTracking=detail" does not cause a segmentation fault


FREQUENCY : always