Re: SIGSEGV

[Ron Michael Khu <ronkhu@ntsp.nec.co.jp>]

kaushal,
perhaps u can try making use of setjmp.h functions =)
but then perhaps ur application might have done a lot illegal memory 
access...
thus the reason for those SIGSEGV's

mohana sundaram wrote:

>You should not handle SIGSEGV and continue the process execution. The
>result is undefined.  Consider restarting the program afresh if your
>program has to run all the time.
>
>Thanks,
>- Mohan.
>
>
>On Wed, 02 Mar 2005 17:50:28 +0530, kaushal <kaushal@rocsys.com> wrote:
>  
>
>>Hello all,
>>        I have big package which "must" run all the time irrespective of any
>>errors.As a part of that Iam even handling the SIGSEGV.The problem is
>>even if I handle the sigsegv,the handler gets called continuously in an
>>infinite loop as if the signal is being recvd. continuously.How can I
>>solve this issue and make my handle run only once?Does bash has such a
>>mechanism internally?Any suggestions would be very helpful.
>>Thanks in advance.
>>
>>kaushal.
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>    
>>
>
>
>  
>