Carl Mäsak wrote: > GGE has ~1k LOC. (Compare this to November's ~1.6k LOC.) It's at the upper > range of the spectrum of Perl 6 application sizes, and it also creates a > fair amount of objects as it runs. I keep getting failures such as the > above about every 20 h of coding. Usually they go away pretty easily, just > by my changing a character somewhere in the source. I've never tried to > isolate a failure of this sort, because due to their instability, I don't > really know how I'd go about it. They are, however, 'stable' in the sense that > if I run things repeatedly without any changes, the failure occurs in the > same place each time.
There are easier ways to observe segfaults in Rakudo+Parrot that might belong in the same category. For example the mandelbrot scripts from http://github.com/colomon/mandelbrot $ perl6 mandelbrot-color.pl 71 > /dev/null Segmentation fault This is only about 250 lines of code, and does nothing fancy: subroutine calls, arithmetics, a bit of control flow. It just runs quite many of these operations, the command line argument controls how many. For some sizes it segfaults reproducible, for others (even larger numbers) it succeeds, As an incentive to fix it: You can redirect the output into a .pnm file and get a pretty picture if it actually succeeds :-) I'd also like to know if other HLL developers and users see similar problems, or if it's specific to Rakudo. Cheers, Moritz _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
