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 Thu, 11 Jan 2007 18:36:24 GMT
Thanks.  On it..

geir

On Jan 11, 2007, at 7:53 AM, Tim Ellison wrote:

> Done in r495209.
>
> I tweaked the launcher in the classlib/luni subdir for now, even  
> though
> I realize this code is destined to move to jdktools.  This way the  
> move
> is a straight copy from classlib -> jdktools rather than have to fuss
> about merging from both.
>
> Regards,
> Tim
>
> Tim Ellison wrote:
>> I'm going for the record of resurrecting the oldest thread ;-)
>>
>> Having this additional signal handler in the launcher is causing  
>> me pain
>> too, so unless there are objections now I'm going to go ahead and
>> disable it by default, and have an option to enable it for those  
>> that want.
>>
>> Regards,
>> Tim
>>
>> Ivan Volosyuk wrote:
>>> It seems that in cmain.c in function genericSignalHandler() just
>>> removing abort() statement will cause default system handler to
>>> execute pointing the exact place of fault right after printing all
>>> this useless crash info. I have no idea how to obtain property value
>>> in this place to make the abort() conditional. Anyway, I think it
>>> would be much beneficial for developers to have crash by default.
>>> -- 
>>> Ivan
>>>
>>> On 9/22/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
>>>> 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
>>>
>>>
>>


Mime
View raw message