I’ve been searching for a solution to my problem for a long time now that’s why i’m turning to you:
Consider this piece of code:
static char done = 0;
static void sigHandler(void)
{
done = 1;
}
int user_input()
{
return (getchar() == 'q') ? 0 : 1;
}
int main(void)
{
signal(SIGTERM, sigHandler);
signal(SIGINT, sigHandler);
while (user_input() != 0 && !done)
usleep(1000);
printf("exiting\n");
return 0;
}
Expected behavior:
The program exits when user inputs q then enter. If CTRL+C is pressed, it is caught by the sigHandler function which sets the flag ‘done’ to 1 and exits the program.
Observed behavior:
The CTRL+C character is eaten by the getchar() call, and the sigHandler function is never executed. When CTRL+C and then enter is pressed, the sigHandler function is called and the program exits.
Could someone with more experience and knowledge help me on that one?
Thanks for your input 🙂
There IS a way to abort the call without resorting to ugly hacks (contrarily to what Paul R said). You should use
sigaction()withsa_flagsset to0instead ofsignal().Besides, the signal(2) manual says:
Normally, after catching and handling a signal, most (I’m not sure if not all) syscalls will be restarted. This way, after handling the sigint signal, your getchar function will continue as if nothing happened.
You can change this behavior by calling sigaction with
sa_flags=0.This way, after handling SIGINT,
getcharwill return-1and errno will be set to “Interrupted system call” (I don’t remember the constant name right now).You would also have to rewrite your user_input() function to handle the case when returning -1.