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
Perl_ck_stringify: Assertion `!((((kid)->op_sibling) ? (_Bool)1 : (_Bool)0))' failed (op.c:11148) #14627
Comments
From @geeknikBuilt v5.21.11 (v5.21.10-31-g008e8e8) with the following command line: ./Configure -des -Dusedevel -DDEBUGGING -Dcc=afl-gcc -Doptimize=-O2\ -g && AFL_HARDEN=1 make -j8 test-prep Bug found with AFL (http://lcamtuf.coredump.cx/afl) Valgrind: GDB: Program received signal SIGABRT, Aborted. Hexdump of the 16-byte test case: System Info: Debian 7, Kernel 3.2.65-1+deb7u2 x86_64, GCC 4.9.2, libc 2.13-38+deb7u8 |
From @geeknik |
From @geeknikperl v5.21.7 (v5.21.6-602-ge9d2bd8) just fails like this: syntax error at test24-min line 1, near "0]" |
From @tonycozOn Sun Mar 29 13:43:30 2015, brian.carpenter@gmail.com wrote:
5.21.7 assrted for me too. I bisected with: AFL_HARDEN=1 perl ../bisect.pl --start=v5.18.0 -DDEBUGGING -Dcc=afl-gcc -Doptimize=-O2\ -g --target=miniperl -e 'eval q/qq{@{0]}${}},{})/' which produced: bad - non-zero exit from ./miniperl -Ilib -e eval q/qq{@{0]}${}},{})/ Optimise "@_" to a single join :100644 100644 b4176c78c2e28c85545bc01963c0d9453e200a9b 8231b871e400fce359fa074e21d494111f91714f M embed.h Tony |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Tue, Apr 21, 2015 at 06:29:13PM -0700, Tony Cook via RT wrote:
Now fixed with commit 82269f5 RT #124207: assert failure in ck_stringify() -- |
@iabyn - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for submitting this ticket. The issue should now be resolved with the release today of Perl v5.22, which is available at http://www.perl.org/get.html |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#124207 (status was 'resolved')
Searchable as RT124207$
The text was updated successfully, but these errors were encountered: