> [EMAIL PROTECTED] - Thu Feb 03 13:24:32 2005]:
>
> On Thu, Feb 03, 2005 at 03:15:35PM -0000, Benjamin Smith wrote:
> > Below is a short program which segfaults with 5.8.5 and 5.8.6. On
> > 5.6.1 the second print shows $op as undef, but there is no segfault.
>
> Thanks for the report. The bug is still present in bleedperl, and can be
> reduced to the following:
>
> my $ip = 0;
>
> while ($ip < 2) {
> if ($ip++) {
> goto X;
> }
> next;
> X:
> } continue { }
>
> The segfaults happens during loop exist because earlier, the goto is
> popping two BLOCKs rather than one:
>
> $ ./perl -Dstvl /tmp/p
>
> ...
>
> (/tmp/p:6) nextstate
>
> STACK 0: MAIN
> CX 0: BLOCK =>
> CX 1: LOOP =>
> CX 2: BLOCK =>
> CX 3: BLOCK =>
>
> (/tmp/p:7) goto
> Unwinding block 3, type BLOCK
> Unwinding block 2, type BLOCK
> (/tmp/p:7) TOPBLOCK scope 4 at pp_ctl.c:2551
>
> STACK 0: MAIN
> CX 0: BLOCK =>
> CX 1: LOOP =>
>
> (/tmp/p:7) nextstate
>
> However, I havn't got time at the moment to look into this further; got to
> design the lighting for a play next week, and my supply of potential
> displacement activites far exceeds the meager hours I have left before
> the deadline. If another P5Per wants to run with this, be my guest...
>
> Dave.
>
>
It looks like this has been fixed in bleadperl, but I'm not sure when.
[EMAIL PROTECTED]:~/sandbox$ ~/perl-current/perl rt_34035.pl
>ARRAY(0x8193f68)<
>ARRAY(0x8193f68)<
