signal handler problems


 
Thread Tools Search this Thread
Top Forums Programming signal handler problems
# 1  
Old 10-07-2005
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:
Code:
void handle_sigint()
{
        write(2,"handling sigint\n",16);
        write(1,"\nshell% ",8);
}

and here is how I am assigning it:
Code:
signal(SIGINT,handle_sigint);

I do this right at the beginning of the code.

Now if I give it SIGINT, the function gets called and I get the correct output on screen - but only once. The second time that I give it ctrl-C, the shell exits.

Should I be doing anything else in the handler to allow for subsequent trapping of SIGINT?

I am working on HP-UX 11.11 PA-RISC.

Last edited by blowtorch; 10-07-2005 at 05:11 PM.. Reason: to add OS info
# 2  
Old 10-07-2005
You should not use signal() for new code. But if you do, you must repeat the call to signal as the first line in the signal handler. The signal goes back to the default action each time with signal(). This is dumb and that is why no one uses signal() anymore.

Ideally, use sigaction() instead. Then whether or not the signal get reset each time is controlled with a flag and you do not want to set that flag.
# 3  
Old 10-07-2005
Thanks Perderabo.. Actually went through the man page for sigaction, but it seemed like such a lot of work... and I was being a bit lazy. But guess I dont really have a choice. Well, back to the code!
# 4  
Old 08-19-2007
doubt in understanding the signal handler

Establishing the signal handler
----------------------------------
signal (SIGALRM, catch_alarm);

Calling the signal handler
-------------------------
catch_alarm (int sig)
{
keep_going = 0;
signal (sig, catch_alarm);
}

The above codes are just the signal handling snippet from the larger program.

Please explain how the call of the signal handling functions here. how the signal inside catch_alarm gets called when no argument is passed while establishing the handler.
# 5  
Old 08-26-2007
Adding to Perderabo's comment on using newer semantics of signal handling instead of older semantics.

Using signal function, while executing the code block within the signal handler there is no guarantee that another signal of the same type delivered would be handled the same way; instead the second signal of the same type delivered would default to its default action which in most of the cases would be to terminate.

for example:

Code:
signal code block {
/*  code instruction is currently here */  <== this instruction point
}

when its at the " this instruction point " and if a signal is again delivered at this point, proper house keeping operations intended for the signal handler will not be completed.

But this never happens with the newer semantics with sigaction,
when the code instructions are executed within the signal action block kernel guarantees that it will not deliver the same signal type until the signal action block is completed.

so with the newer semantics you are guaranteed that your house keeping operations are done.
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. Programming

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... (6 Replies)
Discussion started by: sree_ec
6 Replies

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

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

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

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

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