Revision as of 13:25, 7 May 2013

Description

This test case tests the functionality of the ABRT command line interface.

If you are running through the set of ABRT test cases you probably have a bunch of crash reports in cache. If not, then crash some applications with the command kill -SIGSEGV (pid). Make sure they are not applications containing important data!
Make sure you have abrt-cli installed: su -c 'yum install abrt-cli'

Run abrt-cli list to show unreported crashes
Run abrt-cli list --full to show all crashes
Try crash reporting: run report-cli -e report_Logger -- DIR to report a crash to e.g. Logger
- Select reporting using Logger
Run abrt-cli rm DIR to delete the report

Option list shows all not-yet-reported crashes
Option list --full shows all crashes
Option report shows crash report and asks for confirmation before sending it
- ABRT asks you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then analyzes the crash and creates a report. When the report is ready, abrt-cli opens a text editor with the content of the report. You can see what's being reported, and you are able to fill in instructions on how to reproduce the crash and other comments.
- You are asked if you want to execute some reporter plugins or not.
Option rm deletes crash

@@ Line 9: / Line 9: @@
 # Run {{command|abrt-cli list}} to show unreported crashes
 # Run {{command|abrt-cli list --full}} to show all crashes
-# Try crash reporting: run {{command|abrt-cli report <tt>DIR</tt>}} to report a crash to e.g. Logger
+# Try crash reporting: run {{command|report-cli -e report_Logger -- <tt>DIR</tt>}} to report a crash to e.g. Logger
 #* Select reporting using Logger
 # Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report