chromatic wrote: > On Sunday 29 June 2008 06:52:12 [EMAIL PROTECTED] wrote: > >> Modified: >> trunk/languages/perl6/tools/test_summary.pl >> >> Log: >> [rakudo]: >> * Update test_summary.pl script to use -G, >> record aborted test runs as failed tests. >> Modified: trunk/languages/perl6/tools/test_summary.pl >> =========================================================================== >> --- trunk/languages/perl6/tools/test_summary.pl (original) >> +++ trunk/languages/perl6/tools/test_summary.pl Sun Jun 29 06:52:09 2008 >> @@ -58,7 +58,7 @@ >> } >> close($th); >> printf "%s%s..%4d", $tfile, '.' x ($max - length($tfile)), $plan; >> - my $cmd = "../../parrot perl6.pbc $tfile"; >> + my $cmd = "../../parrot -G perl6.pbc $tfile"; >> my @results = split "\n", `$cmd`; >> my ($test, $pass, $fail, $todo, $skip) = (0,0,0,0,0); >> my %skip; > > This change bugs me; are there other tickets for segfaults and crashes in > Parrot affecting Rakduo besides RT #56448, or am I misunderstanding the > purpose of the change?
I know of #55782. From time to time I encounter some GC weirdnesses, but so far I didn't care to report them all, because I have no way of to know if they have all the same root or not. And as long as even the simplest programs in rakudo (like '1') fail with the gcdebug runcore I don't really know how to identify an offending construct in Perl 6 (if there is one). > If the default behavior is to work around problems, I fear that we won't get > the problems fixed. (See also "Why alternate runcores break far too > frequently.) > > -- c -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/
