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
$=x~0 segfaults Perl 5.24.0-RC1-2-gde1d2c7 #15279
Comments
From @geeknikWhile fuzzing Perl v5.24.0-RC1-2-gde1d2c7 with American Fuzzy Lop, I found that perl -e '$=x~0' triggers a segfault. Perl v5.14.2 dies with "panic: memory wrap at test05.pl line 1." Starting program: /home/geeknik/perl/perl test05.pl Program received signal SIGSEGV, Segmentation fault. ==13016== Invalid write of size 1 |
From zefram@fysh.orgBrian Carpenter wrote:
This doesn't depend on $=. Any two-character string will do: $ perl -lwe 'print "ab" x ~0' It's specific to length 2: $ perl -lwe 'print "abc" x ~0' The panic for length 1 is obviously a different problem. It's specific to -zefram |
The RT System itself - Status changed from 'new' to 'open' |
From @tonycozOn Sun Apr 17 16:31:11 2016, brian.carpenter@gmail.com wrote:
As with #128001, this appears to have been fixed by 6bbd724. Can you reproduce it with blead? Tony |
From @iabynOn Sun, Jun 05, 2016 at 09:34:12PM -0700, Tony Cook via RT wrote:
Yes, that commit was explicitly a fix for [perl #127915], but I only -- |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127915 (status was 'resolved')
Searchable as RT127915$
The text was updated successfully, but these errors were encountered: