diff options
| author | Denys Vlasenko <dvlasenk@redhat.com> | 2011-04-22 00:11:26 +0200 |
|---|---|---|
| committer | Denys Vlasenko <dvlasenk@redhat.com> | 2011-04-22 00:11:26 +0200 |
| commit | 4b3cb55883bfcb90002da0c21a8c39ac79843b92 (patch) | |
| tree | 0c7606b91a211372f1cb961767b6c619a84174c8 /src/plugins/ccpp_events.conf | |
| parent | 65ede0e06ac3d9ce1e9857231a22b97baa1d3954 (diff) | |
| download | abrt-4b3cb55883bfcb90002da0c21a8c39ac79843b92.tar.gz abrt-4b3cb55883bfcb90002da0c21a8c39ac79843b92.tar.xz abrt-4b3cb55883bfcb90002da0c21a8c39ac79843b92.zip | |
renamed abrt-action-analyzecore.py -> analyze-core; made .conf file more readable
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Diffstat (limited to 'src/plugins/ccpp_events.conf')
| -rw-r--r-- | src/plugins/ccpp_events.conf | 40 |
1 files changed, 25 insertions, 15 deletions
diff --git a/src/plugins/ccpp_events.conf b/src/plugins/ccpp_events.conf index 0c6d0462..dcfab55e 100644 --- a/src/plugins/ccpp_events.conf +++ b/src/plugins/ccpp_events.conf @@ -1,23 +1,33 @@ -EVENT=post-create analyzer=CCpp abrt-action-analyze-c -EVENT=post-create analyzer=CCpp abrt-action-list-dsos.py > dsos +EVENT=post-create analyzer=CCpp + abrt-action-analyze-c && + abrt-action-list-dsos.py >dsos # We run analyze_foo steps only if backtrace is empty (not yet generated): -EVENT=analyze_LocalGDB analyzer=CCpp backtrace= abrt-action-trim-files -f 4096m:/var/cache/abrt-di # 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-analyzecore.py --core="$DUMP_DIR/coredump"; abrt-action-install-debuginfo -EVENT=analyze_LocalGDB analyzer=CCpp backtrace= abrt-action-generate-backtrace -EVENT=analyze_LocalGDB analyzer=CCpp backtrace= abrt-action-analyze-backtrace -EVENT=analyze_RetraceServer analyzer=CCpp backtrace= abrt-retrace-client batch -k --dir "$DUMP_DIR" -EVENT=analyze_RetraceServer analyzer=CCpp backtrace= abrt-action-analyze-backtrace +EVENT=analyze_LocalGDB analyzer=CCpp backtrace= + abrt-action-trim-files -f 4096m:/var/cache/abrt-di && + abrt-action-analyze-core.py --core="$DUMP_DIR/coredump" && + abrt-action-install-debuginfo && + abrt-action-generate-backtrace && + abrt-action-analyze-backtrace + +EVENT=analyze_RetraceServer analyzer=CCpp backtrace= + abrt-retrace-client batch -k --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-trim-files -f 4096m:/var/cache/abrt-di -EVENT=reanalyze_LocalGDB analyzer=CCpp abrt-action-analyzecore.py --core="$DUMP_DIR/coredump"; abrt-action-install-debuginfo -EVENT=reanalyze_LocalGDB analyzer=CCpp abrt-action-generate-backtrace -EVENT=reanalyze_LocalGDB analyzer=CCpp abrt-action-analyze-backtrace -EVENT=reanalyze_RetraceServer analyzer=CCpp abrt-retrace-client batch -k --dir "$DUMP_DIR" -EVENT=reanalyze_RetraceServer analyzer=CCpp abrt-action-analyze-backtrace +EVENT=reanalyze_LocalGDB analyzer=CCpp + abrt-action-trim-files -f 4096m:/var/cache/abrt-di && + abrt-action-analyze-core.py --core="$DUMP_DIR/coredump" && + abrt-action-install-debuginfo && + abrt-action-generate-backtrace && + abrt-action-analyze-backtrace + +EVENT=reanalyze_RetraceServer analyzer=CCpp + abrt-retrace-client batch -k --dir "$DUMP_DIR" && + abrt-action-analyze-backtrace -EVENT=report_Bugzilla analyzer=CCpp abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf +EVENT=report_Bugzilla analyzer=CCpp + abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf |