From Fedora Project Wiki

m (moved QA:Testcase abrt Logger to QA:Testcase ABRT Logger: upper case letters for name shortcut)
m (added restart ABRT instructions)
Line 17: Line 17:
 
CCpp = Logger, Mailx
 
CCpp = Logger, Mailx
 
</pre>
 
</pre>
 +
Restart ABRT: <pre># service restart abrt </pre>
 +
 +
And final steps are:
 
# Ensure that the ''crash-catcher'' and ''cc-applet'' processes are both running
 
# Ensure that the ''crash-catcher'' and ''cc-applet'' processes are both running
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package

Revision as of 19:35, 17 August 2009

Description

This test case tests the functionality of the Crash Catcher feature using the Logger plugin.


How to test

  1. Edit /etc/crash-catcher/crash-catcher.conf to enable and activate the Logger plugin. A sample config is noted below
# Enable GPG check
EnableOpenGPG = no
# GPG keys
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
# blacklisted packages
BlackList = bash, bind, apache2
# enabled plugins
EnabledPlugins = SQLite3, CCpp, Mailx, Logger
# selected DB plugin
Database = SQLite3
# reporters association
CCpp = Logger, Mailx

Restart ABRT:

# service restart abrt 

And final steps are:

  1. Ensure that the crash-catcher and cc-applet processes are both running
  2. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  3. Click on the panel applet to start cc-gui
  4. Select the entry matching the recently crashed application, select Forward
  5. At the report window, click Apply

Expected Results

  1. A crash log should be reported by the Logger plugin into /var/log/crash-catcher-logger