> Any thoughts on how to debug this segmentation fault in gdb? You might try to run valgrind on lilypond, ignoring the zillions of warnings regarding Scheme (or use a valgrind suppress file -- a few years ago Han-Wen has posted something): This should give you the `hot spot' which causes the segfault.
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
