1ABRT-ACTION-GENERA(1)             ABRT Manual            ABRT-ACTION-GENERA(1)
2
3
4

NAME

6       abrt-action-generate-core-backtrace - Generates coredump-level
7       (debuginfo-free) backtrace
8

SYNOPSIS

10       abrt-action-generate-core-backtrace [-v] [-d DIR]
11

DESCRIPTION

13       This tool uses coredump from the file coredump and binary at the path
14       stored in file executable in the problem directory to generate
15       coredump-level backtrace.
16
17       Coredump-level backtrace resembles ordinary backtrace in that it
18       contains information about call frames present on the stack at the time
19       of the crash. However, it only contains information that can be
20       obtained from the coredump without debugging symbols available - mainly
21       relative addresses of the stored instruction pointers. Such backtrace
22       can still be useful for reporting and reproducing the bug and does not
23       require debugging information files to be installed. See FILE FORMAT
24       for the description of the generated file.
25
26       The result is saved in the problem directory in a file named
27       core_backtrace.
28
29   Integration with libreport events
30       abrt-action-generate-core-backtrace can be used as an analyzer for
31       application crashes which dump core.
32
33       Example usage in report_event.conf:
34
35           EVENT=analyze analyzer=CCpp
36                   abrt-action-generate-core-backtrace
37

OPTIONS

39       -d DIR
40           Path to problem directory.
41
42       -v
43           Be more verbose. Can be given multiple times.
44

FILE FORMAT

46       The generated file is a text file containing one line for each stack
47       frame of the thread that most likely caused the crash. The line has
48       following format:
49
50           BUILD_ID OFFSET SYMBOL MODNAME FINGERPRINT
51
52       Where:
53
54       BUILD_ID
55           Build ID of the binary file the address is mapped to as a
56           hexadecimal string.
57
58       OFFSET
59           Offset from the start of the executable section of aforementioned
60           file the stored instruction pointer points to. Number in
61           hexadecimal format.
62
63       SYMBOL
64           Name of the function if it is present in the binary (which is often
65           the case for shared libraries).
66
67       MODNAME
68           Name of the module. Contains name of a library or [exe] if it is
69           the executable.
70
71       FINGERPRINT
72           Fingerprint of the function the instruction pointer points to. Not
73           yet implemented.
74
75       Dash in place of any of the parts indicates that the part is unknown.
76

AUTHORS

78       ยท   ABRT team
79
80
81
82abrt 2.0.8                        06/19/2018             ABRT-ACTION-GENERA(1)
Impressum