ABRT project documentation¶
ABRT is a set of tools to help users detect and report application crashes. It’s 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.
- How ABRT works
- Supported programming languages and software projects
- Installing ABRT
- Debugging ABRT
- Interfacing with ABRT
- Documentation for package maintainers
- Documentation for developers
- Documentation for administrators
- Debugging crashes reported by abrt
- Integration test suite
- Frequently asked questions
- Where does ABRT store the crashes?
- What type of crashes can ABRT handle?
- What to do when ABRT is not able to catch the crash of my application?
- How to enable handling of unpackaged software
- How to enable handling of non-GPG signed software
- How do I list crashes handled by ABRT?
- What is μReport?
- What is tainted kernel and why is my kernel tainted?
- How do I create a private bugzilla ticket?
- How do I enable screencasting?
- Why FAF collects tainted kernel oopses?
- Why is my backtrace unusable?
- How to enable dumping of setuid binaries