Red Hat Bugzilla – Bug 155490
Segmentation faults in Perl_gv_fetchpv(), Perl_find_script(), Perl_sv_gets()
Last modified: 2007-11-30 17:11:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux; en_US) KHTML/3.4.0 (like Gecko)
Description of problem:
Recently I have seen segmentation faults crop up in unattended (cron) perl
scripts. Unfortunately I can not reproduce them interactively.
I set them to create core files and downloaded perl-debuginfo. Attached you
will find some backtraces that might help.
I'm sorry I can not be more specific, please advise.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Have perl scripts in cron (/etc/cron.hourly/ etc)
2.Use BSD::Resource to make them create core files if interrupted
3.Wait for messages in the mail
Actual Results: Perl scripts die from segmentation fault and create core files
Expected Results: They should not die. Perl should never ever see a segfault.
See attached gdb backtraces.
*** Bug 155487 has been marked as a duplicate of this bug. ***
Created attachment 113434 [details]
backtrace of segfault in Perl_sv_gets
Please note that even though this is a segfault in a custom script, they also
happen in one liners like 'perl -p -e"s/\s+$//"'
Created attachment 113435 [details]
segfault in Perl_find_script()
Created attachment 113436 [details]
segfault in Perl_gv_fetchpv() - this one also has local variables
One of the machines hit by this also displays bug #154759 - there might be a
connection. I'm running the 2.6.11-1.14_FC3 kernel on them
In addition to kernel, glibc has also been updated lately. No clue if it could
affect this or not.
Since I turned exec-shield randomization off I do not see these crashes
anymore. I believe this is a kernel issue with fedora's newest 2.6.11-1.14
kernel. As I say in my last comment in bug #154759, I think kernel/exec-shield
people should look at this.
Ville, glibc was changed on a fedora2 machine in November 2004, on the fedora3
on 2005.04.07. The new kernel came on 2005.04.13. That is close, but the
problems started after the new kernel was installed.
Resolving as duplicate.
*** This bug has been marked as a duplicate of 154759 ***