When I execute a program that I work on, it fails with the following message:
... Aborted (core dumped)
However, no core dump is created. Core dumps were written previously, and I don't remember that I changed anything related to it.
Here are the outputs of
ulimit -a (core file size is unlimited):
$ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 30 file size (blocks, -f) unlimited pending signals (-i) 24047 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 99 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 24047 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
- I verified that my user can create files in the current directory.
- I read about
/proc/sys/fs/suid_dumpable. Currently, it is set to 0 on my machine. I tried to change it to 1 or 2 but no difference.
- I also tried to execute the program as root, but that did not make a difference either.
I'm running Arch Linux with a 3.7.8-1 kernel. I also downgraded the kernel, but again no difference. (Unfortunately, I don't remember when I could produce the last successful core-dump.)
Now I'm running out of options. Do you know how I can further analyze why no core dumps are produced?