SIGFPE signal does not terminate and generate core file

Question

According to UNIX advance programming documentation, the SIGFPE signal terminates the program and generates a core file.

Here is my program

#include <unistd.h>
#include <signal.h>
#include <stdio.h>
#include <stdlib.h>

static void sig_fpe(int signo);

int
main()
{
        int pid;

        if(signal(SIGFPE, sig_fpe) == SIG_ERR)
                printf("Signal error\n");

        pid = 10;
        pid = pid / 0;

        exit(0);
}

static void
sig_fpe(int signo)
{
        if(signo == SIGFPE){

                printf("SIGFPE signal catch\n");
        }
}

When I run this program in linux machine, it prints "SIGFPE signal catch" repeatedly and does not terminate. The sample output is

SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
SIGFPE signal catch
.
.
.
.

What is the problem?

You can catch and handle any signal except SIGKILL. It's up to you (your program) what happens next. — John C, May 15 '14 at 05:24

score 3 · Accepted Answer · edited May 23 '17 at 12:14

It's a bit tricky with SIGFPE. When SIGFPE is caught the instruction will be re-executed if you simply return from handler - that's very platform dependant but the man page for signal mentions undefined behavior.

See here: Unix signals doubt - on the execution of the below progem

If you want core file as well, you will need to re-install the default signal handler, see Linux: handling a segmentation fault and getting a core dump, and enable core files (on Unix it is done with ulimit -c ...)

SIGFPE signal does not terminate and generate core file

1 Answers1