Learning about signals, I found out that calling the <stdlib.h> functionabort(void); in a C program, which roughly equals to raising a SIGABRT signal, doesn't create a core file on my Ubuntu 13.04 despite having set ulimit -c to unlimited and receiving a core dumped message.

Following the signal(7) manpage , I killed a running instance of yes with all the signals marked with the Core flag, whose default action is declared to be the termination of the process and dumping the core.

Out of all the signals mentioned (SIGILL, SIGABRT, SIGFPE, SIGSEGV, SIGBUS, SIGSYS, SIGTRAP, SIGXCPU, SIGXFSZ, SIGIOT, SIGQUIT), however, only SIGQUIT caused the creation of a core file.

Is this documented and / or configurable behaviour, or is it a quirk?

  • 1
    A bit of introduction should be helpful in my opinion for someone who doesn't know what you are trying to accomplish.
    – Aditya
    Oct 16, 2013 at 10:28
  • Good thinking, I added an introduction.
    – Witiko
    Oct 16, 2013 at 11:11


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.