Bug 546049

Description of problem:
Basically, if you are trying to debug a program, it is useful to be able to find the core file.  ABRT grabs core files and store them in /var/cache/abrt
The release notes make no mention of this.  

Version-Release number of selected component (if applicable):
0.11 Fri 20 Nov 2009 John McDonough

How reproducible:
Very.

Steps to Reproduce:
1. Create a program that causes a seg fault.
2. Compile program.
3. Run program.
4. Read Segmentation fault (core dumped)
5. Look for core dump.  Hm.  Not in current directory.
6. Look at release notes.  
  
Actual results:
4.1.3. ABRT
The ABRT automatic bug reporting tool replaces bug-buddy and kerneloops in the Fedora 12 desktop. ABRT has an extensible architecture and can not only catch and report segmentation faults and kernel oops, but also python backtraces. In contrast to bug-buddy, it can catch segmentation faults in any binary, not just GTK+ applications.
If you have manually modified the GConf settings for the bug-buddy GTK+ module before, you may see warning messages like the following from GTK+ applications:

Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or directory

To stop these messages, run the following command in a terminal in your session:

gconftool-2 --type bool --set /apps/gnome_settings_daemon/gtk-modules/gnomebreakpad false


Expected results:
4.1.3. ABRT
The ABRT automatic bug reporting tool replaces bug-buddy and kerneloops in the Fedora 12 desktop. ABRT has an extensible architecture and can not only catch and report segmentation faults and kernel oops, but also python backtraces. In contrast to bug-buddy, it can catch segmentation faults in any binary, not just GTK+ applications.
If you have manually modified the GConf settings for the bug-buddy GTK+ module before, you may see warning messages like the following from GTK+ applications:

Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or directory

To stop these messages, run the following command in a terminal in your session:

gconftool-2 --type bool --set /apps/gnome_settings_daemon/gtk-modules/gnomebreakpad false

The ABRT tool captures debug information (including coredumps) in the directory /var/cache/abrt.  


Additional info:
This may arguably be a bug in ABRT as well since a coredump from a non-system executable (i.e. something where  rpm -qf ../foo reports 
file /home/username/foo is not owned by any package) is not something that should be ABRT should be doing anything special with.