I have a problem where a Python process is hitting a segmentation fault but not producing a core file.
The following is a toy example that does not produce a core file on the following distros:
- Ubuntu 12.10
- Fedora 18
but does produce core files on the following distros:
- Scientific Linux 6
- Mac OS X
$ python -c 'import time; time.sleep(120)'&
$ kill -abrt $! +
Aborted python -c 'import time; time.sleep(120)'
$ ls core* ls: cannot access core*: No such file or directory
However, if I send a similar signal to a
sleep instance I do get a core file:
$ sleep 120 &
$ kill -abrt $!
+ Aborted (core dumped) sleep 120
$ ls core*
On my Fedora 18 box, here is my
$ cat /proc/sys/kernel/core_pattern
And I've set the following:
$ ulimit -c
This is reproducible regardless of whether the
abrtd service is running or not.
I'm pretty sure I've missed some basic configuration, but I don't know what. Thanks!
EDIT: This may be solvable by running:
$ echo 1 >/proc/sys/fs/suid_dumpable