> [EMAIL PROTECTED] - Wed Aug 31 01:38:30 2005]:
>
>
> This is a bug report for perl from [EMAIL PROTECTED],
> generated with the help of perlbug 1.35 running under perl v5.8.7.
>
>
> -----------------------------------------------------------------
> Hi, i've found a small code that triggers a segfault on the
> following perl versions :
>
> 5.8.4 (ubuntu package)
> 5.8.7 (debian testing package)
> 5.8.7 (freebsd port 5.3-RELEASE)
> 5.9.1 (compiled on my linux debian testing i386, gcc-4.0.1)
>
> unaffected versions :
> version 5.005_03 built for sun4-solaris
>
> Priority is low, since this code is incorrect, but it might help
> resolving other issues.
>
> the segfault does not appear when not using 'strict'.
> note that no code is executed since it's in a sub that is never
> called at runtime.
>
> -- CODE BEGINS HERE --
> #!/usr/bin/perl
> use strict;
> sub s { open $X, my $Y, r; }
> -- CODE ENDS HERE --
>
This appears to have been fixed in bleadperl. I'm not sure, though,
what the exact fix was. Using perl-current, I get:
> ./perl -Mstrict -wle'sub s { open $X, my $Y, r; }'
Global symbol "$X" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
In the 5.8 releases, the coredump occurs in Perl_ck_open.
#0 0x0809964c in Perl_ck_open ()
(gdb) bt
#0 0x0809964c in Perl_ck_open ()
#1 0x08092698 in Perl_convert ()
#2 0x08089336 in Perl_yyparse ()
#3 0x0806731a in Perl_my_failure_exit ()
#4 0x08068d0e in perl_parse ()
#5 0x0805fda9 in main ()
