EVENT=post-create analyzer=CCpp             abrt-action-analyze-c
EVENT=post-create analyzer=CCpp             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

# 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=report_Bugzilla analyzer=CCpp         abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf