bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Abrupt end of interpreting music (segmentation fault)


From: Phil Holmes
Subject: Re: Abrupt end of interpreting music (segmentation fault)
Date: Sat, 18 Feb 2012 13:09:58 -0000

"PrzemysławPawełczyk" <address@hidden> wrote in message news:address@hidden
Hello,

recently I was hit by a bug, and for the first time it's some code bug,
i.e. nothing related to how LilyPond engraves its input. Unfortunately I
cannot provide tiny example as I don't know how to create such (w/o
understanding origin of the bug).

Below you have output from gdb, but unfortunately your dev builds don't
have debugging symbols (maybe it's worth to consider adding them).

Reading symbols from /home/przemoc/lilypond/usr/bin/lilypond...(no
debugging symbols found)...done.
(gdb) set args ./strange-bug-strip.ly
(gdb) run
Starting program: /home/przemoc/lilypond/usr/bin/lilypond
./strange-bug-strip.ly
GNU LilyPond 2.15.30
Processing `./strange-bug-strip.ly'
Parsing...
Interpreting music... [8][16]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000618a31 in ?? ()

To avoid sending enormously long mail I put related files to:
http://paste.przemoc.net/lilypond/abrupt-end-of-interpreting-music/

There are 3 files:
- strange-bug-strip.ly
- lilypond-2.14.2.out
- lilypond-2.15.30.out

If you'll look at lilypond-2.15.30.out you may notice something strange.
It apparently works! Yes, it works if you redirect output to a file.
What you see in lilypond-2.14.2.out though is the same as the output
from normal run (w/o stdout/stderr redirection).

Some interesting remark follows, but not sure whether it's a really
useful one. You can get rid of segfault by any of following methods (and
possibly some more):
- remove Dynamics line from from pianoStaff
- remove \score with \layout
- remove \score with \midi
- remove notes from piccoloStaff
- remove \piccoloStaff from \score with \layout
- remove \key from from global
- remove \time and \tempo from global

I'm on Linux now, but the bug originally hit me on Windows in LilyPond
2.15.27 (don't know whether redirection helps there as I noticed this
workaround just now).

Regards.

P.S. Please add me to CC as I'm not on the list.

--
Przemysław 'Przemoc' Pawełczyk
http://przemoc.net/


If I run this from the Windows command line, it compiles without problem. Do you think it might have anything to do with articulate? The other strange thing is the bar-check fails in your output - I don't see those, either.

--
Phil Holmes
Bug Squad





reply via email to

[Prev in Thread] Current Thread [Next in Thread]