On Sunday 30 December 2007 09:31:55 James Keenan via RT wrote: > Could this be related to a TAP::Parser problem?
That seems unlikely to me; the assertion comes from the internals of Parrot. More likely some sort of memory corruption. Can someone seeing this do a binary search to see which revision triggered the failure? -- c
