Signal Handler Hangs


 
Thread Tools Search this Thread
Top Forums Programming Signal Handler Hangs
# 1  
Old 03-16-2010
Signal Handler Hangs

Hi,

I have a problem with signal handler algorithm in linux. My code is hanging ( It is continuously looping inside the signal handler) . I am pasting my code here...
Please provide me some help regarding this. I googled many places and wrote this code.. but doesnt seem to be working without exit(0).. but i guess this is not the right way. What could be wrong?

Code:
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>

struct sigaction oldHandler;

void myHandler(int sig,  siginfo_t *siginfo, void *context) {
// if i have not written any code inside this function, the program will give a feel of hang( this functions is getting continuously called
        if(siginfo->si_code == SEGV_MAPERR)
        {
                write(1,"address not mapped to object",strlen("address not mapped to object"));
        }
        else if (siginfo->si_code == SEGV_ACCERR)
        {
                write(1,"invalid permissions for mapped object",strlen("invalid permissions for mapped object"));
        }

       write(1,"\n",1);

 //        exit(0); if this exit(0) is not present, program will get continuous calls to this signal handler
        return;
}

int main(int argc, char *argv[]) {

    /* Install mySignalHandler for SIGSEGV */
    struct sigaction sigAct;
    int              status = 0;
    char *addr = NULL;

    sigAct.sa_handler   = 0;
    sigAct.sa_sigaction = myHandler;
    sigfillset(&sigAct.sa_mask);
    sigAct.sa_flags = SA_SIGINFO;

    status = sigaction(SIGSEGV, &sigAct, &oldHandler);
    if (status != 0) {
        perror("Failed to install handler for signal SIGSEGV");
        exit(1);
    }
#if 1
    /* This will invoke the signal handler */
// addr = malloc(strlen("Hello"));
     strcpy(addr,"Hello");
    printf("%s\n",addr);

#endif
        printf("Returning from main\n");
    return 0;
}

# 2  
Old 03-16-2010
Your code keeps getting SIGSEGV. Since you don't resolve the problem that caused the SIGSEGV, when your handler returns your code just gets another SIGSEGV.
# 3  
Old 03-16-2010
hi,
thanks.. but how does it keep on getting signal 11?
the strcpy() function will get one signal 11, that i can understand..
Do you mean internally(deep inside strcpy()) it is getting signal 11???

also could you please tell me how to avoid this subsequent signals. Because in sig handlers, i cannot do a lot of work or can call malloc() or any other unsafe function. So how do i avoid the subsequent signal 11's?

I tried commenting the printf() after strcpy() but it is still getting infinite number of signal 11....
# 4  
Old 03-16-2010
Most unix implementations have the equivalent of an interrupt stack.
SIGSEGV is generated by the OS, not by your process.

TOP:
Your code tries to access out-of-bounds memory. The OS does not allow this, it raises SIGSEGV instead. SIGSEGV signal calls your signal/interrupt handler on the interrupt stack. As soon as the signal handler exits, the interrup stacks pops the offending instruction off the interrupt stack. Then the old, exact same, offending machine code instruction resumes right where it left off - So
goto TOP

Signals do not cure problems. They alert you to them.
# 5  
Old 03-17-2010
@jim mcnamara

Thank you for the explanation.Smilie
It means the same instruction which would have caused trouble keeps on getting to the execution point and OS alerts me infinite times.

So , this would be the case for all SIGSEGV/SIGBUS cases. Then can anyone tell me what could be the best possible algorithm to handle these types of signals.

Would it be anything like

1. Check the reason for signal.
2. Alert user/ get information for debugging
2. Terminate execution from the signal handler itself.(if i return from sig handler, it means that i am eligible for another signal, isn't it?)


Regards,
Sree
# 6  
Old 03-18-2010
Quote:
Originally Posted by sree_ec
@jim mcnamara

Thank you for the explanation.Smilie
It means the same instruction which would have caused trouble keeps on getting to the execution point and OS alerts me infinite times.

So , this would be the case for all SIGSEGV/SIGBUS cases. Then can anyone tell me what could be the best possible algorithm to handle these types of signals.

Would it be anything like

1. Check the reason for signal.
2. Alert user/ get information for debugging
2. Terminate execution from the signal handler itself.(if i return from sig handler, it means that i am eligible for another signal, isn't it?)


Regards,
Sree
On some platforms, you won't get infinite recursion: the process shall be terminated. But anyway you have to account of that possibility, as you experienced it hardly. The way I usually deal with signal caused by HW exception in signal handler is:

- log whatever I can to locate the problem post-mortem. This could be for instance the address of the IP (Instruction Pointer) that generates the exception, or better of stack frame, or even fire a debugger (if you can afford it). Make sure however to only call functions that can be safely used in signal handlers (POSIX calls them async-signal-safe).

- restore the default signal handler for the signal caught.

- return from the handler.

The return from the handler triggers again the exception, but that time the default signal handler is called, causing normally process termination (and usually, a core dump too).

HTH,
Loïc.
# 7  
Old 03-19-2010
MySQL @^

Thank you all for the details.
I understood the concept. Smilie

regards,
sree
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Serial port signal(IRQ) handler (using C)

Hello, I'm writing some serial(UART) handler but have stuck on few issues, maybe anyone can help to show me what I'm doing wrong. Basically I'm intending to write serial RX signal handler. Application receives defined packages of data over serial which contains header and payload. Handler... (3 Replies)
Discussion started by: Lauris_k
3 Replies

2. Programming

problem in doing coding of signal handler

i m unble to execute code of signal handler using a) Wait b) Waitpid (1 Reply)
Discussion started by: madhura
1 Replies

3. Shell Programming and Scripting

Perl Signal Handler

I was working on some Perl code that does signal handling and I came across this one liner and wasn't sure what it was doing. local $SIG{__DIE__} = sub {$! = 2; die $_;}; I think the first part of the anonymous subroutine is setting $! to 2, but I am not sure what the second part is doing. ... (1 Reply)
Discussion started by: SFNYC
1 Replies

4. Shell Programming and Scripting

Perl - Problems with Signal Handler

I have a problem with signal handlers not working. I have a long 1000 line code and somehow this code for signal handling is not working: $SIG{INT} = \&interrupt; sub interrupt { print STDERR "Caught a control c!\n"; exit; # or just about anything else you'd want to do } Any... (2 Replies)
Discussion started by: som.nitk
2 Replies

5. Programming

Problem with signal handler and interrupted system call

Hi, I have a daq program that runs in an infinite loop until it receives SIGINT. A handler catches the signal and sets a flag to stop the while loop. After the loop some things have to be cleaned up. The problem is that I want my main while loop to wait until the next full second begins, to... (2 Replies)
Discussion started by: soeckel
2 Replies

6. Programming

Usage of exit() inside a signal handler

Is it ok to use exit() inside a signal handler? I catch SIGUSR1 in a signal handler and I try to close a file and then exit. The result is inconsistent. Sometimes the process exit and sometimes it returns to the original state before the signal handler was invoked. Perhaps exit is not legal in... (8 Replies)
Discussion started by: Tuvia
8 Replies

7. Programming

Runaway SIGALRM signal handler

I have written a program to demonstrate a problem I have encountered when using BSD style asynchronous input using the O_ASYNC flag in conjunction with a real time interval timer sending regular SIGALRM signals to the program. The SIGIO handler obeys all safe practices, using only an atomic update... (8 Replies)
Discussion started by: stewartw
8 Replies

8. Programming

signal handler problems

Hey guys, I am trying to write a little shell, and was writing a signal handler to handle SIGINT (I am using 'stty intr ^C' and using ctrl-C to give SIGINT). I wrote this signal handler: void handle_sigint() { write(2,"handling sigint\n",16); write(1,"\nshell% ",8); } ... (4 Replies)
Discussion started by: blowtorch
4 Replies

9. Programming

signal handler for SIGCHLD

Hi, I have an c++ application which uses the function fork and execvp(). The parent does not wait until the child ends. The parents just creates children and let them do their stuff. You can see the parent program as a batch-manager. I have added a SIGCHLD handler to the program: void... (3 Replies)
Discussion started by: jens
3 Replies

10. Shell Programming and Scripting

shell script signal handler

AIX 4.3.3 I am trying to write a signal handler into a ksh shell script. I would like to capture the SIGTERM, SIGINT, and the SIGTSTP signals, print out a message to the terminal, and continue executing the script. I have found a way to block the signals: #! /bin/ksh SIGTERM=15 SIGINT=2... (2 Replies)
Discussion started by: jalburger
2 Replies
Login or Register to Ask a Question