Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1107728 +++
+++ 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 DB_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 DB_File;
use threads;
use threads::shared;
my %dbtest;
tie(%dbtest, 'DM_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]
[...]
----
DB_File (BerkeleyDB binding) in RHEL-6 is affected too (perl(DB_File) = 1.820
included in perl-5.10.1-136.el6).
(In reply to Petr Pisar from comment #2)
>
> *** This bug has been marked as a duplicate of bug 1104827 ***
It isn't. This is a report against RHEL-6, while bug #1104827 is against RHEL-7.
Indeed, perl-5.10.1-141.el6_7.1 does crash. This is because RHEL-6 contains fixes for NDBM_File, GDBM_File, and AnyDBM_File, but it's missing a fix for DB_File. It looks like the DB_File fix was omitted by accident.
Thank you for testing my builds.