blob: 0f574713670e941a367a28205338fcca76add603 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
EVENT=post-create analyzer=CCpp
abrt-action-analyze-c &&
abrt-action-list-dsos.py -m maps -o dsos
# We run analyze_foo steps only if backtrace is empty (not yet generated):
# TODO: can we still specify additional directories to search for debuginfos,
# or was this ability lost with move to python installer?
EVENT=analyze_LocalGDB analyzer=CCpp backtrace=
abrt-action-analyze-core.py --core=coredump -o build_ids &&
abrt-action-install-debuginfo --size_mb=4096 &&
abrt-action-generate-backtrace &&
abrt-action-analyze-backtrace
EVENT=analyze_RetraceServer analyzer=CCpp backtrace=
abrt-retrace-client batch --dir "$DUMP_DIR" &&
abrt-action-analyze-backtrace
# Same as "analyze", but executed when user requests "refresh" in GUI
# It doesn't check that backtrace is empty:
EVENT=reanalyze_LocalGDB analyzer=CCpp
abrt-action-analyze-core.py --core=coredump -o build_ids &&
abrt-action-install-debuginfo --size_mb=4096 &&
abrt-action-generate-backtrace &&
abrt-action-analyze-backtrace
EVENT=reanalyze_RetraceServer analyzer=CCpp
abrt-retrace-client batch --dir "$DUMP_DIR" &&
abrt-action-analyze-backtrace
EVENT=report_Bugzilla analyzer=CCpp
abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf
|
