Comment #8 on issue 1800 by brownian.box: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
2.15.9 gives three-staff-system for that snippet. Last three measures
are strange. Is this ok? Should it become another issue?
Updates:
Status: Verified
Comment #9 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
This bug was the segmentation fault. Since you were able to get output,
then the bug is fixed.
The three-staff system, and
Comment #10 on issue 1800 by n.putt...@gmail.com: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
I've been intending to put the attached correction on the LSR.
Thanks, I've updated the snippet.
___
bug-lilypond
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_9
Comment #7 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
Fixed with the pair of commits 7aa537da5 9ff88d127
Updates:
Status: Started
Owner: k-ohara5...@oco.net
Comment #4 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
The Beam now remembers which Staff it started in, so that it can be
engraved by that Staff.
Updates:
Labels: Patch-new
Comment #5 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
The patch at http://codereview.appspot.com/4830064 is done.
No regression tests change
(except that the beams in beam-skip.ly
Updates:
Labels: -Patch-new Patch-review
Comment #6 on issue 1800 by pkx1...@gmail.com: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
Passes make and reg tests
___
bug-lilypond mailing list
On Wed, 03 Aug 2011 05:02:59 +, lilyp...@googlecode.com wrote:
Comment #1 on issue 1800 by k-ohara5...@oco.net: Segfault compiling
LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
% Tinyfying the example leads us to cross staff beams
%
\score {
{ \context Staff = up c8 c
mike at apollinemike.com writes:
On Wed, 03 Aug 2011 05:02:59 +, 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
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1800 by colinpkc...@gmail.com: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
User Tim Reeves (tim.ree...@tokamerica.com) reports:
I tried to compile the Creating music with Scheme
Comment #1 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
% Tinyfying the example leads us to cross staff beams
%
\score {
{ \context Staff = up c8 c %\noBeam % noBeam prevents segfault
\change Staff = down c c
11 matches
Mail list logo
