Debugging ABRT¶
Check steps described in What to do when ABRT is not able to catch the crash of my application?. If this won’t solve your problem proceed with steps described on this page.
ABRT log messages¶
Look for failures in system log:
journalctl | grep abrt
or if your system doesn’t support journal:
grep abrt /var/log/messages
- Possible reasons for abrt not handling crashes might include:
abrtd
not running due to permission errorsDUP_OF_DIR: <dir>
your crash is a duplicate of previous crashExecutable '<exe>' doesn't belong to any package and ProcessUnpackaged is set to 'no'
— see How to enable handling of unpackaged software- Your package is not GPG signed — see How to enable handling of non-GPG signed software
- Crashing executable has setuid bit set — see How to enable dumping of setuid binaries
abrtd¶
If abrtd
malfunctions try stopping it and running it in foreground with verbose mode enabled:
systemctl stop abrtd
abrtd -vvv -d
If it hangs use gdb
to attach to it and produce a backtrace:
gdb /usr/sbin/abrtd $( pidof abrtd ) -batch -ex 'bt full'