Originally created by: *anonymous
Originally created by: colingh...@gmail.com
Jeff Barnes reports:
http://lists.gnu.org/archive/html/lilypond-user/2012-05/msg00582.html
The following music doesn't compile on the mac and causes a segfault on Linux.
Environments:
Mac OSX Lion
Ubuntu 12.04
LilyPond Versions
2.14.2-1 (mac)
2.14.2-2 (ubu from apt-get)
Command from ubu:
address@hidden:~/mac/Documents/apc/music$ lilypond WhenILookIntoYourHoliness.ly
GNU LilyPond 2.14.2
Processing `WhenILookIntoYourHoliness.ly'
Parsing...
Interpreting music...
Interpreting music... [8][16][24][32]Segmentation fault (core dumped)
There was no core file in the directory. Ubuntu sent a crash report yesterday.
Notes:
1) There is no error message when compiling (Cmd+R) on the mac. It silently
fails.
2) If you uncomment out the lines indicated and comment out the lines following
it will compile (2 places in the file).
3) if you remove the music after the problem areas, keeping the voice structure
intact, it will compile.
Any help appreciated.
Jeff
Originally posted by: colingh...@gmail.com
Jeff's lilypond source is attached to this comment.
Originally posted by: colingh...@gmail.com
Link to a further discussion of this bug report:
http://lists.gnu.org/archive/html/bug-lilypond/2012-05/msg00170.html
Originally posted by: gra...@percival-music.ca
1. there is no such thing as lilypond 2.14.2-1 which supports osx lion, so the Mac part is irrelevant.
2. can somebody try this in 2.15.x ? we're not going to have any more 2.14 releases, and a lot has changed since then.
Summary: Lilypond segfaults on Ubuntu
Originally posted by: k-ohara5...@oco.net
This example crashes 2.14.2 on Windows; 2.15.37 succeeds. So probably this is an already-fixed bug.
I'll ask on -user for help to cut it down to a minimal example.
Originally posted by: k-ohara5...@oco.net
(No comment was entered for this change.)
Summary: Lilypond 2.14.x segfaults
Originally posted by: jbarnes...@gmail.com
Woops. I'm running Snow Leopard 10.6.8. Sorry for the incorrect data.
When I open About LilyPond, it says Version 2.14.2-1. See attached screenshot.
Originally posted by: k-ohara5...@oco.net
I cut the example down as far as the smaller example below, which looks like issue 1800. LilyPond compiled from code just before the issue 1800 fix segfaults on the originally-reported file, while LilyPond just after the issue 1800 fix succeeds.
This bug was present in 2.14.2, and 2.15.0 through 2.15.8
<< \new Staff = "trbl" {
\relative c' { \new Voice {
\change Staff = "bss"
<d fis,>8 <fis a,>
\change Staff = "trbl"
<a d,> <d fis,>
<fis a,>2 } } }
\new Staff = "bss" { } >>
Labels: fixed_2_15_9
Mergedinto: 1800
Status: Duplicate
Originally posted by: plros...@gmail.com
I believe it's a duplicate of issue 2030. If nobody wants to fix errors in the 2.14 branch and make new stable releases, I see no point in opening new issues for Lilypond 2.14. Another person would waste time on it, find the fix, propose the backport, nothing would be done, the ticket would be closed and so on, ad nauseum. Either Lilypond 2.14 should be officially declared obsolete, or there should be backports and stable releases.