Issue 380: cycling markup reference segfaults http://code.google.com/p/lilypond/issues/detail?id=380
Comment #10 by hanwenn: GUILE has stack checking, but you need to #define it during the GUILE compile , IIRC. It uses the C stack. Also, it has a performance penalty: every GUILE function call needs to be checked for possible stack overflow. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
