RFR: 8263636: Add --disableregistry option to jhsdb debugd [v2]

[Yasumasa Suenaga]

On Tue, 6 Apr 2021 04:08:51 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

>> Sorry, the correct commands are as follows:
>> 
>> * console 1 (start RMI registry)
>>     * `jhsdb debugd --pid 40859`
>> * console 2 (add `--disableregistry` to use it in console 1)
>>     * `jhsdb -J-Dsun.jvm.hotspot.rmi.serverNamePrefix=second debugd --disableregistry --pid 40860`
>
> Is this the actual use case you are trying to address (registry already started by a debugd process). If yes, then I think that's the best approach for the test. If no, what is the use case? If it's some random application starting the registry, will there be issue related to it not having been started with `--add-modules=jdk.hotspot.agent`?

I updated testcase. Could you review again?

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

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