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
Created attachment 892659 [details] File: backtrace
Created attachment 892660 [details] File: cgroup
Created attachment 892661 [details] File: core_backtrace
Created attachment 892662 [details] File: dso_list
Created attachment 892663 [details] File: environ
Created attachment 892664 [details] File: exploitable
Created attachment 892665 [details] File: limits
Created attachment 892666 [details] File: maps
Created attachment 892667 [details] File: open_fds
Created attachment 892668 [details] File: proc_pid_status
Created attachment 892669 [details] File: var_log_messages
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.
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.