+++ This bug was initially created as a clone of Bug #1107542 +++ +++ This bug was initially created as a clone of Bug #1104827 +++ Description of problem: Perl script using SDBM_File module is core dumping. Seems to match this upstream bug: https://rt.perl.org/Public/Bug/Display.html?id=61912#txn-515026 [...] Steps to Reproduce: Create reproducer test script sdbm_test.pl containing the following lines, as described in the upstream bug report: #!/usr/bin/perl use strict; use Fcntl; use SDBM_File; use threads; use threads::shared; my %dbtest; tie(%dbtest, 'SDBM_File', "test.db", O_RDWR|O_CREAT, 0666); for (1 .. 2) { my $thr = threads->new(\&testThread, $_); $thr->detach(); } sleep 4; sub testThread { my $n = shift; print "thread #" . $n . " started\n"; } Make script executable and run which produces the following output: [root@util6vm ~]# chmod u+x sdbm_test.pl [root@util6vm ~]# ./sdbm_test.pl Expected results: No errors. Actual results: thread #1 started thread #2 started *** glibc detected *** /usr/bin/perl: double free or corruption (out): 0x0000000000e2c2c0 *** ======= Backtrace: ========= /lib64/libc.so.6[0x3d2ca76166] /lib64/libc.so.6[0x3d2ca78c93] /usr/lib64/perl5/auto/SDBM_File/SDBM_File.so(XS_SDBM_File_DESTROY+0xc0)[0x7f9d58fb06f0] [...] --- Additional comment from Petr Pisar on 2014-06-05 05:56:58 GMT --- This happens with any perl, even the development version. ---- All Fedoras are affected.
Created attachment 907071 [details] Proposed fix rebased to 5.18.2
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
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.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
This is fixed in Fedora 22.