Revision as of 17:04, 29 March 2011

Description

This test case checks whether ABRT blacklisting of certain packages works correctly.

Edit the config file /etc/abrt/abrt.conf and find the lines:
# Blacklisted packages

BlackList = nspluginwrapper,valgrind,strace,avant-window-navigator
Add a package whose application you can conveniently crash to the list or crash one from the current list
Restart abrt with the command su -c 'systemctl restart abrtd.service'
Run one of the blacklisted commands - e.g. run strace sleep 3m - and then kill the application from the newly blacklisted package with the command kill -SIGSEGV $(strace_pid)

ABRT should ignore the crash of the blacklisted application
Look to /var/log/messages for 'abrt[6443]: saved core dump of pid 6428 (/usr/bin/strace)' and 'Corrupted or bad dump /var/spool/abrt/ccpp-... (res:2), deleting'

@@ Line 6: / Line 6: @@
 #: BlackList = nspluginwrapper,valgrind,strace,avant-window-navigator
 # Add a package whose application you can conveniently crash to the list or crash one from the current list
-# If changed anything, restart ABRT with the command {{command|su -c 'service abrtd restart'}}
+# Restart abrt with the command {{command|su -c 'systemctl restart abrtd.service'}}
-# Run  - e.g. run {{command|strace sleep 3m}} - and then kill the application from the newly blacklisted package with the command {{command|kill -SIGSEGV $(strace_pid)}}
+# Run one of the blacklisted commands - e.g. run {{command|strace sleep 3m}} - and then kill the application from the newly blacklisted package with the command {{command|kill -SIGSEGV $(strace_pid)}}
 |results=
 # ABRT should ignore the crash of the blacklisted application