New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"warn" causes segmentation fault in Encode #8928
Comments
From vincent-perl@vinc17.netCreated by vincent@vinc17.orgThe following script causes a segmentation fault: #!/usr/bin/env perl use strict; my $encoding = langinfo CODESET; my $agrave = chr(0xe0); $ ./warntest The backtrace: (gdb) bt There seems to be something wrong with the backtrace. With 5.8.7, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343831 Perl Info
|
From @smpetersOn Thu Jun 14 03:57:22 2007, vincent <!-- x --> at vinc17.org wrote:
I can't reproduce this problem, but I also don't know what version of perl -MEncode -wle'print $Encode::VERSION' Thanks! |
The RT System itself - Status changed from 'new' to 'open' |
From vincent-perl@vinc17.netOn 2007-06-29 09:05:41 -0700, Steve Peters via RT wrote:
$ perl -MEncode -wle'print $Encode::VERSION' Note: the module is provided by the Debian perl package (current -- |
From vincent-perl@vinc17.netNote: this is even worse with the C locale: vin% locale -- |
From @smpetersOn Fri Jun 29 09:25:45 2007, vincent <!-- x --> at vinc17.org wrote:
Can you replicate the problem with the most recent version available on |
From vincent-perl@vinc17.netOn 2007-06-29 13:58:10 -0700, Steve Peters via RT wrote:
Same problem (here under Mac OS X): prunille% perl -MEncode -wle'print $Encode::VERSION' -- |
From vincent@vinc17.netWith perl 5.10.0 and 5.10.1, I no longer get a segmentation fault, Encoding: ISO-8859-1 without a newline, and under UTF-8 locales: Encoding: UTF-8 -- |
From @jkeenanOn Thu Oct 29 08:56:06 2009, vincent@vinc17.net wrote:
There has been no correspondence in this RT in more than four years. Tonight I built Perl blead with -Dusethreads and -Duselargefiles on the Dromedary server, then ran the OP's program. This was the output: ##### Is there still a problem which needs addressing? Thank you very much. |
From vincent@vinc17.netOn 2013-12-15 18:58:28 -0800, James E Keenan via RT wrote:
No, everything is OK (both with ISO-8859-1 and with UTF-8) in This bug can be closed. -- |
From @jkeenanOn Mon Dec 16 10:18:03 2013, vincent@vinc17.net wrote:
Closing per request from OP. Thank you very much. |
@jkeenan - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#43214 (status was 'resolved')
Searchable as RT43214$
The text was updated successfully, but these errors were encountered: