Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
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 '13 at 10:28
Good thinking, I added an introduction. – Witiko Oct 16 '13 at 11:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.