[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: |
Keith OHara |
Subject: |
Re: Issue 1800 in lilypond: Segfault compiling LSR 346 |
Date: |
Thu, 4 Aug 2011 05:24:04 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
<mike <at> apollinemike.com> writes:
> On Wed, 03 Aug 2011 05:02:59 +0000, lilypond <at> googlecode.com wrote:
> > http://code.google.com/p/lilypond/issues/detail?id=1800
> >
> This bug results from 0c5927ef30c9f9a9ddec37cc2b9e660695d27303. Joe -
> any ideas on how to fix it?
>
Well, the whole point of that patch was to have beams remember their original
Staff and 'announce' themselves there. The problem here is that the original
Staff has gone away before the beam is finished.
We want a way to remember the original context, but refrain from accessing the
Context object if it has been freed (or whatever they call it in C#).
We don't actually need to announce on the original Staff if the beam really did
cross staves, only in the case where the beam ends just before its Voice
changes
staves.
- 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, 2011/08/03
- 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