Super User is a question and answer site for computer enthusiasts and power users. 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

My configuration.

$ cat /proc/sys/kernel/core_pattern 
$ cat /proc/sys/kernel/core_pipe_limit 
$ cat /proc/sys/kernel/core_uses_pid 
$ selinuxenabled && echo enabled || echo disabled
$ ps aux | grep abrt
500       2192  0.0  0.1 251036  5640 ?        S    10:01   0:00 abrt-applet
500       5673  0.0  0.0 109252   884 pts/0    S+   10:29   0:00 grep --color=auto abrt
$ ulimit -c

What I do.

I start my program in a gnome-terminal with bash. It doesn't get daemonized or detached. Then I do the following from another terminal killall -ABRT <program_name>. The program ends leaving message Aborted. No core file can be found on filesystem.

How this situation can be helped? What else can I do or check?

share|improve this question
up vote 1 down vote accepted

Solution is found.

The problem was with core_pattern, since my program somehow changed it's cwd to / and, thus, can't write anything to filesystem root.

Process cwd can be seen under /proc/<pid>/cwd.

So, I changed core_pattern with echo '/tmp/core.%p' > /proc/sys/kernel/core_pattern and it helped.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .