harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [classlib][launcher] Signal handler disabling
Date Fri, 22 Sep 2006 17:46:38 GMT
This can't be that hard.  Maybe a simple command-line flag

   -launcher:something

Give it a wack and see what happens...

geir


On Sep 22, 2006, at 1:29 PM, Ivan Volosyuk wrote:

> Exactly. I would like to have a way to disable the crash handler
> invoked in the call.
> It is quite painful to locate crashing place when the crash handler
> enabled. Even setting breakpoint in the handler doesn't help - stack
> at this place has number of system frames without debug information
> which hide the actual problematic point.
> --
> Ivan
>
> On 9/22/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
>> Do you mean sig_protect in cmain.c?
>>
>> geir
>>
>> On Sep 22, 2006, at 12:22 PM, Ivan Volosyuk wrote:
>>
>> > Hi,
>> >
>> > While working on windows on DRLVM I introduced some crash  
>> situation. I
>> > found out that there are two active crash handlers. One in  
>> DRLVM, the
>> > other in launcher/classlib.
>> >
>> > I can disable DRLVM's one: -Dvm.assert_dialog=1
>> > But the launcher's crash handler still prevent me to use  
>> debugger to
>> > locate exact place of access violation in VM code. Is it  
>> possible to
>> > disable it somehow?
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message