doczkal / rpms / abrt

Forked from rpms/abrt 4 years ago
Clone

Blame SOURCES/0225-vmcore-generate-reason-file-in-all-cases.patch

b225ea
From ef62408248f975dab68f99e1be1eb9836374dc7c Mon Sep 17 00:00:00 2001
b225ea
From: Jakub Filak <jfilak@redhat.com>
b225ea
Date: Fri, 27 Mar 2015 10:51:52 +0100
b225ea
Subject: [PATCH] vmcore: generate 'reason' file in all cases
b225ea
b225ea
If kdump generates the dmesg log file (vmcore-dmesg.log), the vmcore's
b225ea
post-create event doesn't generate 'reason' file. It is caused by
b225ea
inappropriate use of 'abrt-dump-oops' where the event uses that helper
b225ea
to parse the log file to generate 'backtrace' file instead of using it
b225ea
with the '-u' argument to update the dump directory and create all
b225ea
necessary files.
b225ea
b225ea
Resolves: rhbz#1250337
b225ea
b225ea
Signed-off-by: Jakub Filak <jfilak@redhat.com>
b225ea
---
b225ea
 src/plugins/vmcore_event.conf | 2 +-
b225ea
 1 file changed, 1 insertion(+), 1 deletion(-)
b225ea
b225ea
diff --git a/src/plugins/vmcore_event.conf b/src/plugins/vmcore_event.conf
b225ea
index 34608d9..5957b3f 100644
b225ea
--- a/src/plugins/vmcore_event.conf
b225ea
+++ b/src/plugins/vmcore_event.conf
b225ea
@@ -3,7 +3,7 @@ EVENT=post-create analyzer=vmcore
b225ea
         # If kdump machinery already extracted dmesg...
b225ea
         if test -f vmcore-dmesg.txt; then
b225ea
             # ...use that
b225ea
-            abrt-dump-oops -o vmcore-dmesg.txt >backtrace || exit $?
b225ea
+            abrt-dump-oops -u $DUMP_DIR vmcore-dmesg.txt || exit $?
b225ea
             #
b225ea
             # Does "kernel" element exist?
b225ea
             test -f kernel && exit 0
b225ea
-- 
b225ea
1.8.3.1
b225ea