[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1800 in lilypond: Segfault compiling LSR 346
From: |
lilypond |
Subject: |
Re: Issue 1800 in lilypond: Segfault compiling LSR 346 |
Date: |
Wed, 03 Aug 2011 21:29:31 +0000 |
Comment #2 on issue 1800 by address@hidden: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
A more explicit example:
\score { <<
\new Voice {
\context Staff = "up" c8( % oops, the context lasts only for one note
c c
\change Staff = "down" c)
}
\context Staff = "down" s2
}
The fix to issue 1043 causes a beam or slur to remember the context in
which it started. In the case above, that context goes away before the
beam or slur is finished.
Lilypond segfaults while following the chain of parent contexts, in
Engraver::announce_grob (Grob_info inf)
{ get_daddy_engraver ()->announce_grob(inf); }
http://codereview.appspot.com/4564041/diff/5001/lily/engraver.cc
- Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/02
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/03
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346,
lilypond <=
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/06
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/06
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/06
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/12
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/31
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/31
- Re: Issue 1800 in lilypond: Segfault compiling LSR 346, lilypond, 2011/08/31