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

I noticed that on a 12.04 system setting ulimit -c unlimited and sending Ctrl+\ does not have the expected result.

Though the shell prints

^\zsh: quit (core dumped)

no core dump is written as far as I can tell.

The file /proc/sys/kernel/core_pattern contains an apport pipe - thus, it seems that by default apport is now responsible for writing core dumps.

The directory /var/crash does not contain a recent core dump for my application.

Thus my question: Is apport ignoring SIGQUIT induced core dumps?

If yes:

  • Shouldn't that be considered a bug?
  • How can I configure apport such that it does not ignore SIGQUIT?

(As a workaround setting /proc/sys/kernel/core_pattern to core works as expected, i.e. I get a core dump named core into my CWD after hitting SIGQUIT.)

share|improve this question
up vote 2 down vote accepted

Yes, apport is ignoring SIGQUIT and yes, it's a bug IMO.

I reported it in with a patch, and a fix has been released.

share|improve this answer

Apport filters coredumps on SIGQUIT. You'll find a discussion on Launchpad about that issue (dumps core on SIGQUIT). There are good arguments to change this behaviour, but is not clear if Ubuntu will do it.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.