On Fri, Oct 22, 2010 at 3:02 PM, Carl Sorensen <[email protected]> wrote: > As near as I can tell, this code is triggering an infinite loop that fails > when the scheme heap overflows.
Interesting. > arg is *not* a stream-event, it's a music-event. Indeed. But I wasn't expecting it to cause a segfault. > Segfaults are supposed to always be critical errors, but I think that in the > case of incorrect Scheme code, we shouldn't label it as a LilyPond error. I agree. That's why I didn't open a tracker page. Thanks! Valentin. _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
