On Wed, 14 Aug 2024 14:59:33 GMT, Erik Gahlin <[email protected]> wrote:
>> JFR.dump, JFR.start, and JFR.stop are written in Java and have separated
>> from the Hotspot dcmd infrastructure. For example, this is how filename
>> expansion is handled by JFR.start (and -XX:StartFlightRecording):
>>
>> String path = expandFilename(parser.getOption("filename"));
>>
>> Default values are hardwired into the command and the help is custom. The
>> JFR.start command allows additional option, like event settings. that are
>> not "DCmdArguments". One could replace "STRING" with "FILE", but the only
>> visible impact would be the metadata provided by the DiagnosticCommandMBean.
>
> I filed an issue:
> https://bugs.openjdk.org/browse/JDK-8338405
Thanks Erik.
The related JBS entry for dealing with the type names is:
https://bugs.openjdk.org/browse/JDK-8338603
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/20401#discussion_r1722211386
