-
Notifications
You must be signed in to change notification settings - Fork 555
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
Assert fail in op.c without other symptoms: sub{\@0[0]=0} #15363
Comments
From @dcollinsnGreetings Porters, I have compiled bleadperl with the afl-gcc compiler using: ./Configure -Dusedevel -Dprefix='/usr/local/perl-afl' -Dcc='ccache afl-gcc' -Uuselongdouble -Duse64bitall -Doptimize=-g -Uversiononly -Uman1dir -Uman3dir -Dusequadmath -des And then fuzzed the resulting binary using: AFL_NO_VAR_CHECK=1 afl-fuzz -i in -o out bin/perl @@ After reducing testcases using `afl-tmin` and performing additional minimization by hand, I have located the following testcase that triggers an assert fail in debug buids of the perl interpreter. The testcase is the file below. On normal builds, this runs normally (albeit with an expected warning). On debug builds, this returns an assert fail. dcollins@nightshade64:~/perl$ ./perl -Ilib -t -W -e 'sub{\@0[0]=0}' The closing brace is not necessary in order to replicate, and neither is -t, but -W is. Debugging tool output is below. A git bisect was performed and reported the following. 0ca7b7f is the first bad commit \@array[@slice] assignment plus changes to the aelem tests to check rhs context. I did \local @a[@s] at the same time, since I was practically copying :100644 100644 1184bf28927651410830cce06bf2f9018d44f4c2 150d70f3457ae67e43c9ec8bbe82836be0211c19 M op.c **GDB** dcollins@nightshade64:~/perldebug$ gdb --args ./perl -Ilib -W -e 'sub{\@0[0]=0}' Program received signal SIGABRT, Aborted. **VALGRIND** No reported memory management errors. **PERL -V** dcollins@nightshade64:~/perldebug$ ./perl -Ilib -V Characteristics of this binary (from libperl): |
From @iabynOn Thu, May 26, 2016 at 04:33:47PM -0700, Dan Collins wrote:
Fixed by v5.25.2-53-g36efb5a -- |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Mon Jun 27 07:08:15 2016, davem wrote:
Oops. Thank you. (Why did you not add a test?) -- Father Chrysostomos |
From @iabynOn Mon, Jun 27, 2016 at 08:27:28AM -0700, Father Chrysostomos via RT wrote:
Because I'm lazy??? :-) Test added with v5.25.2-60-gc61e103 -- |
@iabyn - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for filing this report. You have helped make Perl better. With the release today of Perl 5.26.0, this and 210 other issues have been Perl 5.26.0 may be downloaded via: If you find that the problem persists, feel free to reopen this ticket. |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#128252 (status was 'resolved')
Searchable as RT128252$
The text was updated successfully, but these errors were encountered: