On Wed, Feb 06, 2008 at 09:59:52PM -0500, Zev Benjamin wrote: > > What happens if you run using "parrot perl6.pbc" instead > > No difference. > > > of the perl6 executable? If you still get the segfault, how > > about trying parrot with the -G option? > > This stops the segfault. > > > > > How about if the code to be executed is read from a file instead > > of being run via interactive mode? > > This also stops the segfault.
This tells me that the problem is likely a GC bug within Parrot somewhere, as opposed to being a problem with rakudo. We see these pop up in various instances from time to time. I'll leave this ticket open for now, in case one of the Parrot GC hackers wants to try to track it down. Thanks! Pm
