# New Ticket Created by jn...@jnthn.net
# Please include the string: [perl #65396]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=65396 >
Hi,
Just been looking at the slice.t failure and tracked it down a bit to a
smaller example. If you run the test under -G it fails in a very
different way. While this one that follows doesn't segfault without -G
(in fact it runs just fine), under -G it fails just like slice.t under -G.
..\..\parrot perl6.pbc -e " my @array = (3,7,9,11); say @array[0..1]"
37
..\..\parrot -G perl6.pbc -e " my @array = (3,7,9,11); say @array[0..1]"
called from Sub 'parrot;Int;succ' pc 5519 (src\classes\Int.pir:83)
called from Sub 'parrot;Perl6Object;' pc 1272 (src\classes\Object.pir:714)
called from Sub 'parrot;Int;succ' pc 5519 (src\classes\Int.pir:83)
called from Sub 'parrot;Perl6Object;' pc 1272 (src\classes\Object.pir:714)
{ repeated many times }
called from Sub 'parrot;Int;succ' pc 5519 (src\classes\Int.pir:83)
called from Sub 'parrot;Perl6Object;' pc 1272 (src\classes\Object.pir:714)
called from Sub 'postfix:++' pc 21516 (src\builtins\op.pir:39)
called from Sub 'parrot;Range;shift' pc 9493 (src\classes\Range.pir:107)
called from Sub 'parrot;Range;' pc 9364 (src\classes\Range.pir:47)
called from Sub 'parrot;List;!flatten' pc 6770 (src\classes\List.pir:228)
called from Sub 'postcircumfix:[ ]' pc 4416 (src\classes\Positional.pir:179)
called from Sub '_block21' pc 852 (EVAL_21:268)
called from Sub '_block14' pc 106 (EVAL_21:65)
called from Sub '!UNIT_START' pc 18218 (src\builtins\guts.pir:386)
called from Sub 'parrot;PCT;HLLCompiler;eval' pc 949
(src\PCT\HLLCompiler.pir:530)
called from Sub 'parrot;PCT;HLLCompiler;evalfiles' pc 1274
(src\PCT\HLLCompiler.pir:691)
called from Sub 'parrot;PCT;HLLCompiler;command_line' pc 1469
(src\PCT\HLLCompiler.pir:792)
called from Sub 'parrot;Perl6;Compiler;main' pc 243078
(src/gen_actions.pir:23278)
I've not got any good guesses just yet as to what on earth is going on
here; anyone else have any ideas? I reckon if we fix this, the segfault
at the exit of slice.t will go away, anyways...it almost seems we are
succeeding because of a GC issue, but in a longer program like the test
script that catches up with us sometime close to the end.
Thanks,
Jonathan
