harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Ellison <t.p.elli...@gmail.com>
Subject Re: [classlib][launcher] Signal handler disabling
Date Fri, 09 Feb 2007 13:44:39 GMT
Gregory Shimansky wrote:
> Mark Hindess wrote:
>> Gregory, why did you want it to be optional?  Do you use this option?
> The reason is quite simple. When VM crashes it is much easier to debug
> it right at the spot of the crash. On Windows it is done with Just In
> Time debugging facility, on Linux core dump is useful. DRLVM with can
> and does detect the condition when crash happens inside of VM and when
> it is ran with -XDassert_dialog=true (default) does not try to do
> anything intelligent like printing stack. This allows debugging at the
> spot of the crash.
> When launcher installs its own handler it catches the crash. Even though
> it can print registers and maybe some stack symbols, it is not as good
> as using full fledged debugger to analyze the problem.

I think Mark meant, if it is optional when would you want to have the
signal hander installed by the launcher?


View raw message