This test case tests the functionality of the ABRT feature.
How to test
- We will check that the KerneloopsScanner, works and provides correct amount of crashes detected.
- Download files:
- Test that stand-alone detector tool is working properly:
$ dumpoops -s oops1.test dumpoops: found oopses: 1 Version: 126.96.36.199-159.fc10.i686 #1 BUG: unable to handle kernel NULL pointer dereference at 00000000 ...
oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.
- Optional. Edit /etc/abrt/abrt.conf so it says:
10 = KerneloopsScannerThis makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:
$ service abrtd restart
- cat the downloaded file to /var/log/messages e.g.:
cat oops1.test >> /var/log/messages
- you'll need root privs for this
- Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
- Open the abrt-gui and check if you can see the oops
- Oopses detected and visible in abrt-gui