ABRT-ACTION-GENERA(1) ABRT Manual ABRT-ACTION-GENERA(1)NAMEabrt-action-generate-core-backtrace - Generates coredump-level
SYNOPSISabrt-action-generate-core-backtrace [-v] [-d DIR]
This tool uses coredump from the file coredump and binary at the path
stored in file executable in the problem directory to generate
Coredump-level backtrace resembles ordinary backtrace in that it
contains information about call frames present on the stack at the time
of the crash. However, it only contains information that can be
obtained from the coredump without debugging symbols available - mainly
relative addresses of the stored instruction pointers. Such backtrace
can still be useful for reporting and reproducing the bug and does not
require debugging information files to be installed. See FILE FORMAT
for the description of the generated file.
The result is saved in the problem directory in a file named
Integration with libreport events
abrt-action-generate-core-backtrace can be used as an analyzer for
application crashes which dump core.
Example usage in report_event.conf:
Path to problem directory.
Be more verbose. Can be given multiple times.
The generated file is a text file containing one line for each stack
frame of the thread that most likely caused the crash. The line has
BUILD_ID OFFSET SYMBOL MODNAME FINGERPRINT
Build ID of the binary file the address is mapped to as a
Offset from the start of the executable section of aforementioned
file the stored instruction pointer points to. Number in
Name of the function if it is present in the binary (which is often
the case for shared libraries).
Name of the module. Contains name of a library or [exe] if it is
Fingerprint of the function the instruction pointer points to. Not
Dash in place of any of the parts indicates that the part is unknown.
· ABRT team
abrt 2.0.8 11/21/2013 ABRT-ACTION-GENERA(1)