Updates:
Labels: -Type-Critical Type-Crash
Comment #34 on issue 2335 by [email protected]: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Keeps head down...
The reason I didn't mark this as a critical regression is that I spent some
time looking at it and discussing it with the reporter before raising it.
I concluded that it's highly likely that it's been in the build for a long
time, and appears and disappears semi-randomly based on factors we don't
understand. We define a regression as something that used to
work "deliberately" in a previous stable release. My contention would be
that whether this input crashed a 64 bit linux build is pure happenstance -
there's no evidence that any change has made this happen.
I'm not suggesting not trying to fix this. Just that, by the rigorous
defintition of critical regression - this isn't one.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
