RFR: 8269225: JFR.stop misses the written info when the filename is only specified by JFR.start [v3]

[Erik Gahlin]

On Thu, 24 Jun 2021 01:59:54 GMT, Denghui Dong <ddong at openjdk.org> wrote:

>> Hi,
>> 
>> Could I have a review of this small fix?
>> 
>> JFR.stop misses the written info when the filename is only specified by JFR.start, for example:
>> 
>> $jcmd 87802 JFR.start name=test filename=2.jfr
>> 87802:
>> Started recording 1. No limit specified, using maxsize=250MB as default.
>> 
>> Use jcmd 87802 JFR.dump name=test to copy recording data to file.
>> 
>> $jcmd 87802 JFR.stop name=test
>> 87802:
>> Stopped recording "test".
>> 
>> 
>> The 'JFR.stop' didn't print written info, but actually, 2.jfr was generated.
>
> Denghui Dong has updated the pull request incrementally with one additional commit since the last revision:
> 
>   update test

Marked as reviewed by egahlin (Reviewer).

-------------

PR: https://git.openjdk.java.net/jdk/pull/4573