Front page | perl.perl5.porters |
Postings from August 2010
At Sat Jul 31 08:31:51 -0400 2010, jettero@cpan.org (via RT) wrote:
> This bug is probably known and fixed. I appologize in advance
> that I don't really know where to check for that. I did flip
> through some git commits and perl deltas trying to decide if the
> bug was really known or incidentally fixed while acheiving other
> goals. In any case, it doesn't apply to more modern perls, but
> 5.10.x seems to be deployed everywhere so it is perhaps worth
> pointing out.
>
> #!/usr/bin/perl
>
> eval { ("3"."x"x25) =~ m/(\d+)(??{ _noexist($^N) })/; 1 }
>
> # the sagfault will occur in whatever happens to be the next op
>
> or warn $@; # SIGSEGV in Perl_pp_warn() or comment line for
> ;print "here\n"; # SIGSEGV in Perl_do_print() instead
>
>
> # 5.6.1 seems unaffected
> # 5.8.1 seems to work but complains: panic: pad_free curpad. after "here"
> # 5.10.1 where I noticed this (ubuntu 10.04)
> # 5.12 seems fine
> # 5.13 also fine
This bug seems to be only trigged with -Dusethreads, and was fixed by
f7461760003db2ce68155c97ea6c1658e96fcd27. Unfortunately, as that was
a fairly complex feature addition, it's not a good contender to be
cherry-picked into maint-5.12.
- Alex
--
Networking -- only one letter away from not working
Thread Previous
|
Thread Next