SIGSEGV

SIGSEGV

[kaushal]

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.

Re: SIGSEGV

[mohana sundaram]

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
> 


-- 
The expert at anything was once a beginner.

Re: SIGSEGV

[Ron Michael Khu]

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
>>
>>    
>>
>
>
>  
>

Re: SIGSEGV

[Glynn Clements]

kaushal wrote:

> 	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?

Install the handler using sigaction() with the SA_RESETHAND flag. When
the signal is received, the handler will be de-installed; if SIGSEGV
is received again, the program will be terminated.

The fact that your program received SIGSEGV suggests that one or more
variables contain an invalid value. If you attempt to resume execution
without fixing the error, you will just get further SIGSEGVs.

More generally, if you detect that your program has got into an
invalid state, you have two reasonable choices: either give up (i.e.
terminate) or correct the problem.

Ignoring the problem and hoping that that the program will magically
recover isn't going to work.

A more realistic approach for programs which need to run continuously
would be to run the program from init with the "respawn" option; if
the program terminates, init will restart it.

-- 
Glynn Clements <glynn@gclements.plus.com>