Bug 1094488

Summary: [abrt] logwatch: do_clean_objs(): perl killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jason M <jason__m>
Component: perlAssignee: Jitka Plesnikova <jplesnik>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: cweyl, frank, iarnell, jplesnik, jsynacek, kasal, perl-devel, ppisar, psabata, rc040203, richardfearn, tcallawa, varekova
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d2afbce20df701dc42d134cbaa7f1dedc49c4086
Whiteboard: abrt_hash:dba28599015cd93ae59b2306062afcadd91b489f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-01 08:20:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jason M 2014-05-05 19:39:37 UTC 
Description of problem:
Actually, I was not aware that a problem occured.  Nevertheless the program desires to file it.  Apparently logwatch is the culprit.

Version-Release number of selected component:
logwatch-7.4.0-30.20130522svn140.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/perl /usr/share/logwatch/scripts/logfiles/cron/applydate
crash_function: do_clean_objs
executable:     /usr/bin/perl
kernel:         3.13.9-200.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 do_clean_objs at sv.c:466
 #1 S_visit at sv.c:422
 #2 Perl_sv_clean_objs at sv.c:577
 #3 perl_destruct at perl.c:766
Comment 1 Jason M 2014-05-05 19:39:40 UTC 
Created attachment 892659 [details]
File: backtrace
Comment 2 Jason M 2014-05-05 19:39:42 UTC 
Created attachment 892660 [details]
File: cgroup
Comment 3 Jason M 2014-05-05 19:39:43 UTC 
Created attachment 892661 [details]
File: core_backtrace
Comment 4 Jason M 2014-05-05 19:39:45 UTC 
Created attachment 892662 [details]
File: dso_list
Comment 5 Jason M 2014-05-05 19:39:46 UTC 
Created attachment 892663 [details]
File: environ
Comment 6 Jason M 2014-05-05 19:39:48 UTC 
Created attachment 892664 [details]
File: exploitable
Comment 7 Jason M 2014-05-05 19:39:49 UTC 
Created attachment 892665 [details]
File: limits
Comment 8 Jason M 2014-05-05 19:39:50 UTC 
Created attachment 892666 [details]
File: maps
Comment 9 Jason M 2014-05-05 19:39:52 UTC 
Created attachment 892667 [details]
File: open_fds
Comment 10 Jason M 2014-05-05 19:39:53 UTC 
Created attachment 892668 [details]
File: proc_pid_status
Comment 11 Jason M 2014-05-05 19:39:55 UTC 
Created attachment 892669 [details]
File: var_log_messages
Comment 12 Petr Pisar 2014-05-07 13:39:14 UTC 
The code crashes because of jumping into invalid address when destroying allocated data structures on perl interpreter exit. This is itself very weird and it can be a symptom of bug in the perl, a memory corruption, or a compiler bug.

Because the the code flow of the logwatch tool depends on the file system content, it's almost impossible to reproduce this crash and thus to debug this problem. E.g., the "/usr/sbin/logwatch --output mail" command proceeds cleanly for me.

I'm sorry, but without more details, especially debugging on your side like narrowing what's the trigger, it's impossible to fix this issue.
Comment 13 Fedora End Of Life 2015-05-29 11:46:03 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.