Bug 132698 - double free or corruption on exit from perl
Summary: double free or corruption on exit from perl
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: perl
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-15 22:20 UTC by Daniel Drucker
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-17 02:48:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Daniel Drucker 2004-09-15 22:20:04 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3)
Gecko/20040913 Firefox/0.10

Description of problem:
glibc throws a "double free or corruption" every time I exit from perl
-MCPAN -e shell

Version-Release number of selected component (if applicable):
glibc-2.3.3-51

How reproducible:
Always

Steps to Reproduce:
glibc-2.3.3-51
perl-5.8.5-4

# perl -MCPAN -e shell    

cpan shell -- CPAN exploration and modules installation (v1.7601)
ReadLine support enabled

cpan> quit
Lockfile removed.
*** glibc detected *** double free or corruption: 0x08610b28 ***
Aborted
# 

Additional info:
Comment 1 Jakub Jelinek 2004-09-15 22:34:08 UTC 
That's double free or corruption in perl...
Comment 2 Daniel Drucker 2004-09-16 01:29:50 UTC 
I get the same error when exiting PINE.
Comment 3 Daniel Drucker 2004-09-16 21:12:37 UTC 
My mistake, the PINE thing was something else.

I have narrowed this down to a problem in perl module Term::ReadLine... 
[dmd@eco ~]$ cat tester.pl
#!/usr/bin/perl

use Term::ReadLine;
my $term = new Term::ReadLine::Gnu;
[dmd@eco ~]$ perl tester.pl
*** glibc detected *** double free or corruption: 0x08107ab0 ***
Aborted
[dmd@eco ~]$
Comment 4 Daniel Drucker 2004-09-16 21:25:01 UTC 
I've sent a note to the listed author of Term::ReadLine::Gnu.
Note You need to log in before you can comment on or make changes to this bug.