bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 2356 in lilypond: Lilypond segfaults


From: lilypond
Subject: Re: Issue 2356 in lilypond: Lilypond segfaults
Date: Mon, 27 Feb 2012 17:23:22 +0000


Comment #1 on issue 2356 by address@hidden: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356

Sorry, that was the wrong suggestion. It's actually the Span_bar_stub_engraver in the StaffGroup context which causes the crash.

Adding

\context {
   \StaffGroup
   \remove "Span_bar_stub_engraver"
}

works for me.

The first bad commit is the one which adds the Span_bar_stub_engraver: 20670d51f8d97fd390210dd239b3b2427f071e7c

It produces a different segfault though, since there was another bug shadowing the current one in Grob::get_vertical_axis_group () (which Mike fixed recently with 70fd22ce9b84f9d3c1d44ffd79baafd370a389fb). Saying that, with the previous commit Haipeng's file seems to enter an infinite loop on my system and Jay's has an assertion failure related to TupletNumber offsets.




reply via email to

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