We always want to know that a crash in packaged binary was detected. Set: OpenGPGCheck = no && restart abrtd service On crash some sort of [ FAIL ] warning with custom created log from /var/spool/abrt/$reporter-$date-$pid/ directory should be produced. But do not generate, by default, backtrace because it's time consuming. Also do not rlBundleLog corefile -- it's quite huge. One can place such a log generating command or link to the script to RunApp() function, e.g. [ Common ] ActionsAndReporters = RunApp("echo abrt: Crash in $(cat package) detected: $(cat reason) | wall", "/tmp/__beakerlib_abrt_crash") Perhaps `/tmp/__beakerlib_abrt_crash` could be socket not just regular file, so abrt can "append" to it. By using wall(1) we can see the msg on stdout (and TESTOUT.log). Ideas? Comments? Code?
Very nice one. We will need to deal with old RHELs (is abrt in RHEL4 / 5 ?), and perhaps also with 'legit/expected' segv/abrts. Some of the tests directly introduce segvs. Probably 'on by default, test can switch it off' approach would work.
(In reply to comment #1) > Very nice one. We will need to deal with old RHELs (is abrt in RHEL4 / 5 ?), RHEL4 no. RHEL5 not yet (and perhaps never will be). > and perhaps also with 'legit/expected' segv/abrts. Some of the tests directly > introduce segvs. Probably 'on by default, test can switch it off' approach > would work. Most segv/abrts are from unpackaged binaries, they won't be caught (by default). There may be some cases when you want to intentionally crash packaged binary (and we are also sure we don't want to fix this "issue", e.g. bug 433662). There may be function `rlAbrtBlacklist $package`, intentionally & temporary blacklisting $package for whole test runtime, and then reverted. Unfortunately, there's no API to call some abrt function and handle it with $package, it would have to be done manually with sed, awk, etc.
I don't think anything new will happen here.