Comment #26 on issue 2335 by [email protected]: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Mike: the bug reporter claimed that he had a tiny example. I called him on
it; he produced another two versions. His final version still looks
large-ish for a segfault.
BUT I HAVE CHECKED THIS. It is sitting in my ~/tmp right now, and after 15
minutes the only thing I have discovered is that I can comment out the
\set PianoStaff.midiInstrument
in pianoStaffMidi and still keep the segfault. Comment out other \set
commands? no segfault. Comment out some music? no segfault. Comment out
the \time 4/4 ? no segfault.
As I said, I would never believe anybody who told me this was happening,
but I've seen it myself. As you know, I'm an absolute bugger when it comes
to proving people wrong, but the *only* think I have found that I can
comment out is that one \set command. This bug really is as strange as he
suggests. I have 8 years of calling users idiots over lilypond, but I
can't do that here.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
