-
Notifications
You must be signed in to change notification settings - Fork 562
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
(regression?) v5.17.6+ segfaulting on simple (buggy) code #12913
Comments
From @garuThis is a bug report for perl from garu@cpan.org, Many thanks to David Leadbeater (dg) for doing the actual work $ cat Boom.pm $ cat boom.sh $ ../perl-bisect/Porting/bisect.pl --target miniperl ~/boom.sh Donât leak subs containing syntax errors I fixed this for BEGIN blocks earlier, but missed the fact that When called without an o argument (from newANONATTRSUB), newATTRSUB :100644 100644 3f71cffc1351b181760b3b22d2bebb5eae5c16d9 dgl@perlqa:~/perl/perl$ git describe 9ffcdca dgl@perlqa:~/perl/perl$ gdb --args ./miniperl ~/Boom.pm Program received signal SIGSEGV, Segmentation fault. Flags: Site configuration information for perl 5.17.10: Configured by garu at Sun Apr 14 11:05:41 BST 2013. Summary of my perl5 (revision 5 version 17 subversion 10) configuration: Platform: Locally applied patches: @INC for perl 5.17.10: Environment for perl 5.17.10: |
From @garuThis is a bug report for perl from garu@cpan.org, Thanks to David Leadbeater (dg) for doing the actual work of $ cat Boom.pm $ cat boom.sh $ ../perl-bisect/Porting/bisect.pl --target miniperl ~/boom.sh Donât leak subs containing syntax errors :100644 100644 3f71cffc1351b181760b3b22d2bebb5eae5c16d9 b2801c7b5f4807886cc293e3fb567a46202b6e4d M op.c dgl@perlqa:~/perl/perl$ git describe 9ffcdca dgl@perlqa:~/perl/perl$ gdb --args ./miniperl ~/Boom.pm Program received signal SIGSEGV, Segmentation fault. Flags: Site configuration information for perl 5.17.10: Configured by garu at Sun Apr 14 11:05:41 BST 2013. Summary of my perl5 (revision 5 version 17 subversion 10) configuration: Locally applied patches: @INC for perl 5.17.10: Environment for perl 5.17.10: |
From @iabynOn Sun, Apr 14, 2013 at 06:19:56AM -0700, Breno G. de Oliveira wrote:
It can be reduced slightly further: BEGIN { Looks like it should be 5.18 blocker. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @maukeOn 15.04.2013 13:06, Dave Mitchell wrote:
A debugging perl fails the assert in gv.c:551 (S_maybe_add_coresub): because GvCV(gv) == NULL. -- |
From @tonycozI bisected this with a debugging perl, and found: bad - non-zero exit from ./perl -Ilib -e eval q[ use strict; $foo; sub { [perl #113712] Don’t create stubs after errors perl5.002beta3 (c07a80f) stopped bodies of subrou- But, instead of making the sub declaration not happen at all, it ended For a full sub declaration (body and all) to create a stub just Likewise, it would be weird if a stub declaration Similarly, a compilation error will cause ‘sub foo {}’ no suppress This commit fixes all this, making things consistent: If there is a :100644 100644 69bd2a4df8cc2eae325ed03e408b0fcc260be241 |
From @tonycozOn Mon Apr 15 04:06:51 2013, davem wrote:
Even simpler: $foo/; # some syntax error Pushed a fix to smoke-me/tonyc/core_lc_error Tony |
From @tonycozOn Thu Apr 25 01:29:45 2013, tonyc wrote:
Fix pushed as a92039c, closing. Tony |
@tonycoz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#117607 (status was 'resolved')
Searchable as RT117607$
The text was updated successfully, but these errors were encountered: