doczkal / rpms / abrt

Forked from rpms/abrt 4 years ago
Clone

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

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