Automatic bug detection and reporting tool
C Shell Python Makefile M4 Augeas Other
Latest commit a07ac44 Oct 25, 2016 @jfilak jfilak build: without args configures for debugging
Simplify live to ABRT newbies. This commit should save some time
developers who do not want to follow "make rpm; rpm -Uvh --force build/*.rpm"

Signed-off-by: Jakub Filak <>
Failed to load latest commit information.
apidoc doc: fix doxygen complaints Feb 22, 2013
augeas limit ourselves to *.conf in /etc/abrt Feb 26, 2014
doc dbus-doc: rewrite the XML to Problems2 Sep 9, 2016
icons icons update Apr 26, 2011
init-scripts abrt-xorg.service: change due to abrt-dump-journal-xorg Nov 6, 2015
po dbus: Problems2 API implementation Sep 9, 2016
scripts fix helper debug build script Oct 23, 2013
src vmcore: fix an undefined variable on error path Oct 19, 2016
tests CI: make debugging easier with more log messages Oct 19, 2016
.dir-locals.el Emacs project-wide code-style settings Apr 12, 2010
.gitignore dbus: Problems2 API implementation Sep 9, 2016 Add basic documentation Mar 11, 2016
COPYING moved files Feb 19, 2009
ChangeLog add end-of-line to a few files which didn't have it on last line Sep 18, 2009 doc: add a guide for ABRT hackers Oct 19, 2016 doc: add a guide for ABRT hackers Oct 19, 2016 testsuite: move examples to 'tests' May 30, 2016 Add basic documentation Mar 11, 2016
abrt-doxygen.cfg doxygen config for abrt Aug 20, 2010 abrt-bodhi: use CCpp PackageManager configuration directive from conf… Aug 5, 2016 spec: update gdb Requires Sep 17, 2016
asciidoc.conf Asciidoc manpage support; abrt-action-mailx manpage May 2, 2011 build: without args configures for debugging Oct 25, 2016
config.mak silent xmlto generation May 5, 2011 tree-wide: make path to GDB configurable Sep 17, 2016
gen-version spec: let configure generate the spec file Mar 16, 2015
zanata.xml translations: update zanata configuration Feb 11, 2016


A set of tools to help users detect and report application crashes.


Its main purpose is to ease the process of reporting an issue and finding a solution.

The solution in this context might be a bugzilla ticket, knowledge base article or a suggestion to update a package to a version containing a fix.


Every ABRT program and configuration file has a man page describing it. It is also possible to read the ABRT documentation online. For contributors and developers, there are also wiki pages describing some topics to deeper technical details.



ABRT consist of several services and many small utilities. While The utilities can be successfully run from the source directories after build, the services often uses the utilities to do actions and expect the utilities installed in the system directories. Hence to run the services, it is recommended to install ABRT first and run them as system services. The instructions how to build and install ABRT can be found in