I have a crashing application, which crashes with the output: Aborted (core dumped).

Now when I look at the directory, containing the binary, there is no crashdump.

  • There is no core directory.
  • There is free space on the filesystem
  • User can create files in the directory.

ulimit -a prints

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31845
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65536
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 31845
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

cat /proc/sys/kernel/core_pattern prints


cat /proc/sys/fs/suid_dumpable prints


Is there anything else I can check? I am out of ideas.

Am running on Ubuntu 15.04.

  • Some OS allow to configure a systemwide directory where to put core files

  • The program may have changed it's working directory. The core file is in the working directory of the program that dumped core

  • If ulimit -c 0 was issued, the shell message should not print "core dumped" unless the OS is buggy

  • The program switched the working directory. – abergmeier Sep 23 '15 at 13:15

Your Answer

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

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