-
Notifications
You must be signed in to change notification settings - Fork 559
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
Encode memory corruption (maybe PerlIO::encoding?) #9966
Comments
From @greergaCreated by @greergaOn Ubuntu's stock perl (what perlbug picked up) and blead 5.11.1 valgrind (blead): valgrind (ubuntu 5.10.0): glibc (ubuntu): glibc (blead): I don't have a stock 5.10.1 handy to test, but if blead and 5.10.0 does Perl Info
|
From @greergaOn Sun, 15 Nov 2009, George Greer wrote:
Test script: - - - 8< - - - 8< - - - (That's supposed to be a single line.) For me, Ubuntu's perl 5.10.0 crashes, blead (GitLive-blead-3146-g88a6f4f) ==17892== Invalid write of size 1 -- |
From [email protected]-----BEGIN PGP SIGNED MESSAGE----- George, Thank you for your report. On 16 Nov 2009, at 13:38, George Greer wrote:
It tries to return DURING string during encoding so the usage is wrong to begin with. perl -MEncode -le 'print encode "ascii", " a\x{b6}\x{2022}a"x8, sub{ "\x{2022}" }' I also found this does not happen in Perl 5.8.9. So this has something to do with how Perl 5.10 allocates memory. At any rate, ext/Encode/Encode.xs must be the file to look at. Dan the Maintainer Thereof iEYEARECAAYFAksA5BYACgkQErJia/WXtBvMiwCdEJ6PbaD8XgC0vXCtL903wu3q |
The RT System itself - Status changed from 'new' to 'open' |
From @greergaOn Mon, 16 Nov 2009, Dan Kogai wrote:
And thank you for being so quick to respond.
It might not crash under perl 5.8.9, but making it crash is finicky ==30569== Command: /home/perl/work/cpan_maint-5.8/perl/bin/perl5.8.9 perl 5.10.0 crashed a lot more than blead 5.11.1 during my test case - - - 8< - - - 8< - - - -- |
From [email protected]-----BEGIN PGP SIGNED MESSAGE----- George, I think I have fixed it now. On 16 Nov 2009, at 14:46, George Greer wrote:
Would you try the patch below? That fixed the problem on my OS X. ====
|
From @greergaOn Mon, 16 Nov 2009, Dan Kogai wrote:
Yes, Valgrind confirms.
Thanks! Obviously trying to give UTF-8 as a fallback character was -- |
From @gannett-ggreerFixed in Encode 2.38. |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#70528 (status was 'resolved')
Searchable as RT70528$
The text was updated successfully, but these errors were encountered: