[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2392 in lilypond: Segfault in connection with
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2392 in lilypond: Segfault in connection with \applyContext |
Date: |
Fri, 30 Aug 2013 07:53:40 +0000 |
Updates:
Cc: jan.nieuwenhuizen address@hidden
Comment #2 on issue 2392 by address@hidden: Segfault in connection with
\applyContext
http://code.google.com/p/lilypond/issues/detail?id=2392
Aaaand here is an even worse one:
\score
{
{
\skip 1
\new Staff { c'1 }
}
\midi {}
}
All of those are pretty clearly caused by lily/score-performer.cc where the
listener for OneTimeStep is called _before_ the listener for Prepare.
Indeed, it would appear that Prepare is _never_ called at all. It's just
that midi reacts more allergic to this than paper.
So the solution obviously should not be to make OneTimeStep robust against
being called without Prepare but rather to fix the iteration logic so that
Prepare _does_ get called.
I'm out of my depth with that one, so Cc to the masters.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Lilypond-auto] Issue 2392 in lilypond: Segfault in connection with \applyContext,
lilypond <=