Or you can let ABRT to do all the necessary work instead of you:Ībrt-action-analyze-ccpp-local enables all *debug* yum repositories, downloads the missing debug info packages, unpacks them in /var/cache/abrt-di/, runs gdb and stores its output in backtrace file.
Action strings bug install#
You can install the debug info data manually via the debuginfo-install command suggested by gdb: An example of getting backtrace from 'coredump' file:ĪBRT does not extract backtrace from a core dump file automatically, because this task requires the debug info data to be available. All the utilities have a name prefixed with "abrt-action", thus you can change the current working directory to a problem directory, type abrt-action and hit Tab key.ģ. In case you want to examine the problem directory manually or you just want to know what the problem is about, ABRT provides you with several tiny utilities doing useful stuff. Lines from the system logs related to this problem List of dynamic libraries loaded at the time of crash Unix timestamp of the first occurrence of this problemĪ core dump file for crashes of compiled programs (C/C++) Number of times this problem has been encountered on a system Rpm package which the executable belongs to The well known path where the problem directories are created is:Īnd the most interesting files within a problem directory follows:Ībsolute path to an executable file experienced this problem Upon a detection of a problem, ABRT creates a directory in a well known path and puts all the gathered data into that directory in form of regular files. The main purpose of the ABRT server is to help the maintainers to prioritize their work and provide users guidance for known or already fixed issues.
Searches for "suspicious" strings in the system logs provides a JNI agent detecting uncaught Java exceptions.registers a handler for uncaught Ruby exceptions.registers a handler for uncaught Python exceptions.registers a core dump program for crashes of C/C++ applications.hooks own crash handlers in the most used programming environments.An example of getting backtrace from 'coredump' file:.