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
Infinite recursion related to die, overloading, s/// and \x{...} #8804
Comments
From @cpansproutIf the following hold true-- - die is called outside an eval --then the substitution operator will automagically call the Here is a test script: #!/usr/bin/perl -lw no warnings 'once'; use Carp 'longmess'; my $x = 'thing'; # any string will trigger the bug $thing = bless []; __END__ If I use s/[a-e]/b/g for the substitution, the bug is not triggered. This bug exists in 5.9.4 as well as 5.8.8. This is a really obscure bug--it took me a while to reproduce it. :-) Flags: Site configuration information for perl v5.8.8: Configured by neo at Tue Jan 9 16:06:53 PST 2007. Summary of my perl5 (revision 5 version 8 subversion 8) configuration: Locally applied patches: @INC for perl v5.8.8: Environment for perl v5.8.8: |
From @cpansproutI've just noticed that the debugging line I added (warn longmess...) Deep recursion on anonymous subroutine at overtest line 10. Line 10 is the line with the substitution. |
From @rgarciaOn 26/02/07, via RT Father Chrysostomos <perlbug-followup@perl.org> wrote:
that is, an Unicode surrogate,
I don't reproduce this with bleadperl; I think that was fixed by |
The RT System itself - Status changed from 'new' to 'open' |
From p5p@spam.wizbit.beOn Sun Feb 25 18:08:34 2007, sprout@cpan.org wrote:
This is still a problem on blead... #!/usr/bin/perl -lw no warnings 'once'; use Carp 'longmess'; my $x = "thing\n"; # any string will trigger the bug $thing = bless []; Doesn't segfault #!/usr/bin/perl -lw no warnings 'once'; use Carp 'longmess'; my $x = "thing\n"; # any string will trigger the bug my $x = "thing\n"; # any string will trigger the bug $thing = bless []; Does segfault But: #!/usr/bin/perl -lw my $x = "thing\n"; # any string will trigger the bug Does not segfault. Kind regards, Bram |
From @cpansproutThis was fixed by the die/eval cleanup in 5.14.0: There are only 'skip'ped commits left to test. |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#41618 (status was 'resolved')
Searchable as RT41618$
The text was updated successfully, but these errors were encountered: