RFR: 8262520: Add SA CommandProcessor support to connect to debug server [v3]
Yasumasa Suenaga
ysuenaga at openjdk.java.net
Thu Mar 4 01:13:04 UTC 2021
On Wed, 3 Mar 2021 22:33:19 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:
> Yes, I'm starting to come to the same conclusion. The only code that constructs a `CLHSDB` object, and therefore triggers the potential call to `doUsage()`, is `CLHSDB.main()`, and it is only called from `SALauncher` when using `jhsdb clhsdb`. We could get rid of `main()` and have some other entrypoint that is passed the values of all the possible options, rather than having to parse them in CLHSDB.java.
>
> There is one test invokes java with the `CLHSDB` class. See SABase.java. It's part of ciReplay testing. I think it would be easily modified to just run `jhsdb clhsdb`
I think `debugd` and `jinfo` are also remove `main()` if they have because they do not provide commands like `jstack`.
I will file it to JBS, and will fix them later.
-------------
PR: https://git.openjdk.java.net/jdk/pull/2773
More information about the serviceability-dev
mailing list