FS#16690 - perl segfaults with Term::ReadLine::Gnu

Attached to Project: Arch Linux
Opened by Markus Pfeiffer (profmakx) - Friday, 16 October 2009, 13:45 GMT
Last edited by Francois Charette (Firmicus) - Wednesday, 21 October 2009, 08:28 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Kevin Piche (kpiche)
Francois Charette (Firmicus)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
With perl-5.10.1-3, readline-6.0.004-1 and Term::ReadLine::Gnu 1.19 from CPAN

/usr/bin/perl -e 'require Term::ReadLine; Term::ReadLine::Gnu->new("test");'

segfaults.
I recompiled perl with -DPERL_USE_SAFE_PUTENV (as suggested in INSTALL) but it did not help. Perhaps someone with more expertise on this could try solving this.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

- Install perl
- Install readline
- Install Term::ReadLine::Gnu

/usr/bin/perl -e 'require Term::ReadLine; Term::ReadLine::Gnu->new("test");'

(produces segfault)
This task depends upon

Closed by  Francois Charette (Firmicus)
Wednesday, 21 October 2009, 08:28 GMT
Reason for closing:  Not a bug
Additional comments about closing:  The real bug is when the very old and defunct package termcap-compat is still installed, it messes the readline configuration.
Comment by Francois Charette (Firmicus) - Monday, 19 October 2009, 09:13 GMT
If recompiling with -DPERL_USE_SAFE_PUTENV does not help, then I fear there is little we can do!
The bug has been reported upstream in any case, see the last entry of:
http://rt.cpan.org/Public/Bug/Display.html?id=37194

Until this gets fixed, use Term::ReadLine instead ;)
Comment by Francois Charette (Firmicus) - Monday, 19 October 2009, 09:28 GMT
Perhaps you had termcap-compat installed? Remove it, and try again!
Here it works without problem.
BTW, I include a PKGBUILD for perl-term-readline-gnu ...
   PKGBUILD (0.7 KiB)
Comment by Markus Pfeiffer (profmakx) - Wednesday, 21 October 2009, 08:19 GMT
Well, thank you very much! Removing termcap-compat solved the problem!
Comment by Francois Charette (Firmicus) - Wednesday, 21 October 2009, 08:25 GMT
Glad it worked. "pacman -Qi termcap-compat" said it was "installed as a dependency for another package", but it no longer was (it has been removed from the repo long ago I guess). It was likewise polluting my system until a few days ago ;)

Loading...