Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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 re

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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? _

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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 _

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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 bug-lilypond@gn

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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 is done. No regression tests change (except that the beams in beam-skip.ly

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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. I

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

apollinemike.com> writes: > On Wed, 03 Aug 2011 05:02:59 +, lilypond 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 t

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

Comment #2 on issue 1800 by k-ohara5...@oco.net: 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"

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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

Re: Issue 1800 in lilypond: Segfault compiling LSR 346

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"

Issue 1800 in lilypond: Segfault compiling LSR 346

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 (