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

[Chris Plummer]

On Tue, 6 Apr 2021 03:32:25 GMT, Yasumasa Suenaga <ysuenaga at openjdk.org> wrote:

>> Both of the above are using `--disableregistry`. Is that what you meant to do? I would think that you would not want that on the first one.
>
> 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`?

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

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