-
Notifications
You must be signed in to change notification settings - Fork 567
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
Segfault on bareword as loop index #14886
Comments
From internationils@gmx.netThis is a bug report for perl from internationils@gmx.net, #!/usr/bin/perl use strict; sub something { my $subvar= shift; } $table = something("$tablename[$loop]_table"); Flags: Site configuration information for perl 5.20.2: Configured by Debian Project at Sun May 3 16:16:25 UTC 2015. Summary of my perl5 (revision 5 version 20 subversion 2) configuration: Locally applied patches: @INC for perl 5.20.2: Environment for perl 5.20.2: |
From @nicomen$ gdb --args perl -e '30; "$a[b]";' Program received signal SIGSEGV, Segmentation fault. |
From [Unknown Contact. See original ticket]$ gdb --args perl -e '30; "$a[b]";' Program received signal SIGSEGV, Segmentation fault. |
From @wolfsageOn Thu, Sep 3, 2015 at 7:51 AM, Nils <perlbug-followup@perl.org> wrote:
I believe this reduces to: perl -e '0; $a[b]' Seemingly broken in 5.19.3 with commit 515abc4 Set PL_curcop to NULL in op.c:S_cop_free Seemingly fixed in 5.21.5, in passing, by: commit f5b5c2a Simplify double-nextstate optimisation [...] -- Matthew Horsfall (alh) |
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgNicolas Mendoza via RT wrote:
That's DECLARE_STORE_LC_NUMERIC_SET_TO_NEEDED(). Presumably failing via -zefram |
From @iabynOn Fri, Sep 04, 2015 at 08:11:04PM +0100, Zefram wrote:
Looking at this further, the SEGV in 5.20.0 happened due the "delete spare The simplified deduplication code introduced by v5.21.4-465-gf5b5c2a So I'll close this ticket. -- |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125972 (status was 'resolved')
Searchable as RT125972$
The text was updated successfully, but these errors were encountered: