Re: Issue 2356 in lilypond: Lilypond segfaults

[lilypond]

Comment #6 on issue 2356 by address@hidden: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356

SCM *v is a recipe for trouble with regard to garbage collection.  It is  
not something that the Scheme garbage collector sees as Scheme.  So the  
variable under it needs to be protected separately.  I'll look some more.

Oh, and Mike?  In my last segfault hunt, I remarked:

Anyway, one thing that has been useful is figuring out "target record" in  
gdb which lets you step backwards from a segfault.  Since various other  
optimizations made the stack backtrace less than useful (since the problem  
occurs with tail jump optimizations, the bad function is not actually  
present in the backtrace), this was quite helpful.

Could be useful for stepping backwards from your segfault to the actual  
cause.