bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0


From: lilypond
Subject: Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Date: Fri, 05 Nov 2010 12:09:19 +0000


Comment #8 on issue 1382 by percival.music.ca: Segfault when setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382

Well, it's not quite "crashing", but since scheme is turing-complete, anybody can write a lilypond file which never finishes processing. With that in mind, I'd be ok with ignoring crashes in scheme code, or maybe even in non-safe tweaks.

But I think that if something could compile under -dsafe mode but crashes, that should still count as a Critical bug.

(I'm not certain if this specific case works under -safe more or not; I'm just making a general observation here)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]