From 4b3cb55883bfcb90002da0c21a8c39ac79843b92 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Fri, 22 Apr 2011 00:11:26 +0200 Subject: renamed abrt-action-analyzecore.py -> analyze-core; made .conf file more readable Signed-off-by: Denys Vlasenko --- src/plugins/ccpp_events.conf | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) (limited to 'src/plugins/ccpp_events.conf') 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 -- cgit