On Mon Jan 21 19:05:10 2008, [EMAIL PROTECTED] wrote: > On Sunday 20 January 2008 21:31:08 Will Coleda via RT wrote: > > > Spent some more time trying to track this down. On OSX/86, I was able to > > reproduce the segfault with much less tcl code: > > > > %cat foo.tcl > > after 10 > > %./tclsh foo.tcl > > > > if I ran: > > > > %../../parrot -G tcl.pbc foo.tcl > > > > The segfault goes away, which smells like a GC issue. > > > > However, I can't duplicate it with --runcode=gcdebug on feather.perl6.nl; > > Any suggestions on a plan of attack? > > What does a binary search of checkins suggest? It might not help > tremendously, but it might give us some idea of what goes kablooie. > > Otherwise, how do you feel about putting on my Hat of Memory Checking and > slogging through my GC debugging guidelines? > > -- c >
This segfault is no longer triggered by tcl; r25851 seemed like a likely culprit for the fix, but reverting it doesn't cause the segfault to come back. I'll open a new ticket if the segfault comes back.
