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:8067: SV *Perl_cv_const_sv_or_av(const CV *const): Assertion `SvTYPE(cv) == SVt_PVCV || SvTYPE(cv) == SVt_PVFM' failed. #16040
Comments
From @dur-randirCreated by @dur-randirWhile fuzzing perl v5.27.1-37-g4c95ee9f29 built with afl and run @I0::""my I0"";sub f00}f00 to cause an assertion failure. This is a regression between 5.20 and commit 0f94cb1 [perl #123223] Make PADNAME a separate type distinct from SV. This should fix the CPAN modules that were failing Unfortunately, it will probably break other CPAN modules, but I think GDB info about the crash location is: (gdb) bt Perl Info
|
From @tonycozOn Sat, 24 Jun 2017 07:01:54 -0700, randir wrote:
The parser appears to be treating the final f00 as the name of a lexical sub, but finding a non-CV in the protocv: (gdb) Tony |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131647 (status was 'open')
Searchable as RT131647$
The text was updated successfully, but these errors were encountered: