table of contents
ABRT-ACTION-GENERA(1) | ABRT Manual | ABRT-ACTION-GENERA(1) |
NAME¶
abrt-action-generate-core-backtrace - Generates coredump-level (debuginfo-free) backtrace
SYNOPSIS¶
abrt-action-generate-core-backtrace [-v] [-d DIR]
DESCRIPTION¶
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.
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 core_backtrace.
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:
EVENT=analyze analyzer=CCpp
abrt-action-generate-core-backtrace
OPTIONS¶
-d DIR
-v
FILE FORMAT¶
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 following format:
BUILD_ID OFFSET SYMBOL MODNAME FINGERPRINT
Where:
BUILD_ID
OFFSET
SYMBOL
MODNAME
FINGERPRINT
Dash in place of any of the parts indicates that the part is unknown.
AUTHORS¶
06/22/2018 | abrt 2.0.8 |