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
op.c:14389: Perl_rpeep: Assertion `(kid->op_type == OP_NULL && ( kid->op_targ == OP_NEXTSTATE || kid->op_targ == OP_DBSTATE )) || kid->op_type == OP_STUB || kid->op_type == OP_ENTER' failed #15823
Comments
From @dur-randirCreated by @dur-randirWhile fuzzing perl v5.25.8-216-gfbceb79751 built with afl and run }my;0=sort{i d&0}0 to cause an assertion failure, even when run under -c for a syntax 932bca2 is the first bad commit OP_SORT: store start of block in null->op_next When a sort with a code block, like sort { BLOCK } arg, ... sort (The 'scope' may be instead be 'ex-leave' depending on circumstances). At run time, pp_sort() navigates its way down from the sort op to find the The main point of this commit however is not the slight speed up from GDB info about the crash location: (gdb) bt Perl Info
|
From @iabynOn Sun, Jan 22, 2017 at 04:18:13AM -0800, Sergey Aleynikov wrote:
Fixed with the following commit. It's yet another example of the commit 03fedef avoid sort assert failure after compile fail -- |
The RT System itself - Status changed from 'new' to 'open' |
@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#130617 (status was 'resolved')
Searchable as RT130617$
The text was updated successfully, but these errors were encountered: