RFR: JDK-8152435: (CL)HSDB should be started with no argument

[Dmitry Samersoff]

Yasumasa,

> Is it allowed?

Hmm. Lets go ahead with SAGetoptException.

-Dmitry

On 2016-04-06 02:15, Yasumasa Suenaga wrote:
> Hi Dmitry,
> 
> Thanks for your comment.
> 
>> So please use DebuggerException in SALauncher.
> 
> DebuggerException will be thrown from many point in
> hotspot/src/jdk.hotspot.agent .
> If SALauncher catches DebuggerException, it will show help message in
> each time.
> 
> Is it allowed?
> 
> 
> Thanks,
> 
> Yasumasa
> 
> 
> On 2016/04/06 0:24, Dmitry Samersoff wrote:
>> Yasumasa,
>>
>> SAGetoptException should be internal for SAGetopt.
>>
>> So please use DebuggerException in SALauncher.
>>
>> PS: Besides that the changes looks OK for me and  I'll sponsor the push.
>>
>> -Dmitry
>>
>> On 2016-03-29 15:02, Yasumasa Suenaga wrote:
>>> PING: Could you review it?
>>>
>>>
>>> Yasumasa
>>>
>>>
>>> On 2016/03/22 23:49, Yasumasa Suenaga wrote:
>>>> HI all,
>>>>
>>>> After JDK-8151709, CLHSDB and HSDB cannot be started with no
>>>> argument via jhsdb.
>>>> CLHSDB and HSDB can attach process / core after starting.
>>>> jhsdb should support it.
>>>>
>>>> I uploaded webrev:
>>>>
>>>>     http://cr.openjdk.java.net/~ysuenaga/JDK-8152435/webrev.00/
>>>>
>>>> This patch passed jtreg test sun/tools/jhsdb in jdk repos.
>>>> Could you review it?
>>>>
>>>> I cannot access JPRT.
>>>> So I need a sponsor.
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Yasumasa
>>>>
>>
>>


-- 
Dmitry Samersoff
Oracle Java development team, Saint Petersburg, Russia
* I would love to change the world, but they won't give me the sources.