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
utf8 + "[a]a{2}" + /$.../ = panic: sv_len_utf8 cache #9026
Comments
From webmasters@ctosonline.orgThe following snippet works in 5.9.4 and earlier but fails in 5.10.0 $ perl -e'$s="[a]a{2}"; utf8::upgrade $s; /$s/; print "ok\n"' Apparently this error occurs when a string to be interpolated in a A binary search points to change #31246 as being the culprit. I hope this helps. Father Chrysostomos perl5.10.0 -Mconstant=Just,0 -le'sub IO::Handle::a_japh{print*{$_[0]} Flags: Site configuration information for perl 5.10.0: Configured by neo at Sun Sep 9 11:55:38 PDT 2007. Summary of my perl5 (revision 5 version 10 subversion 0 patch 31832) Locally applied patches: @INC for perl 5.10.0: Environment for perl 5.10.0: |
From @iabynOn Mon, Sep 10, 2007 at 01:04:59PM -0700, webmasters @ ctosonline. org wrote:
A closer look reveals that that change (one of mine) accidentally The regex/utf8 bug itself is older. I'll try to have a look at it sometime -- |
The RT System itself - Status changed from 'new' to 'open' |
From @demerphqOn 9/10/07, Dave Mitchell <davem@iabyn.com> wrote:
Assuming that was aimed at me Ill note that i have put this in my todo Yves -- |
From @hvdsDave Mitchell <davem@iabyn.com> wrote: So does that mean an error still occurs but is no longer flagged? Hugo |
From @iabynOn Wed, Sep 12, 2007 at 01:53:39PM +0100, hv@crypt.org wrote:
Now fixed by #31867
This enables the former behaviour: ${^UTF8CACHE} = -1; -- |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#45337 (status was 'resolved')
Searchable as RT45337$
The text was updated successfully, but these errors were encountered: