Description

This test case tests the functionality of the ABRT kerneloops feature.

How to test

Warning: This test abuses syslog a bit - don't forget to restart it at the end of the test case.

We will check that the abrt-dump-oops works and provides correct amount of crashes detected.
Download files:
- oops1.test
- not_oops3.test
Test that stand-alone detector tool works properly; Do as a root for both files:
$ abrt-dump-oops -d -o oops1.test

abrt-dump-oops: Found oopses: 1

Version: 2.6.27.9-159.fc10.i686 #1

BUG: unable to handle kernel NULL pointer dereference at 00000000

...

EIP: [<f88dec25>] radeon_cp_init_ring_buffer+0x90/0x302 [radeon] SS:ESP 0068:f0a0cf08

abrt-dump-oops: Creating dump directories
Open abrt-gui and look for the crash.
And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
Make sure /etc/abrt/abrt_event.conf contains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report_kerneloops.org analyzer=Kerneloops abrt-action-kerneloops. And /etc/abrt/abrt.conf contains abrt-dump-oops = abrt-dump-oops -drw /var/log/messages. If changed anything, restart abrtd: service abrtd restart.
Concatenate oops1.test to /var/log/messages e.g.:
```
cat oops1.test >> /var/log/messages
```
If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to emerge to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.

After running abrt-dump-oops on oops1.test crash should be created and visible via abrt-gui and in the terminal.
Running abrt-dump-oops on not_oops3.test should not create crash case.
ABRT should automatically detect OOPS in /var/log/messages and visible via abrt-gui.

Now restart rsyslog service so writing to /var/log/messages works correctly again.