In july, I asked about a problem (
http://lists.gnu.org/archive/html/bug-lilypond/2005-07/msg00104.html )
then in version 2.7.2 but received no answer at all.
Still in all succeding versions, at present 2.7.10, my Lilypond linux
setup (debian unstable/testing) crashes with a segmentation fault just
after the grob count, whenever the script contains \relative. Without
\relative scripts compile flawlessly, producing both pdf and midi. Most
annoying! So at the moment I am stuck with the Windows version only on
another pc.
The bug must lie somewhere in an application, lilypond is calling at
compile time, but which one? Since my first message I have updated to
ESP-Ghostscript 8.15rc4 and reinstalled/reconfigured every python packet
on my box, but without any changes.
How do I debug the behaviour of lilypond at crash-time? The last message
recieved before the crash is the grob count and a number, then the
segmentation fault happens.
--
yours sincerely Villum Sejersen
http://home20.inet.tele.dk/vsevisit
telefon +45 59 91 31 57
mobil +45 30 34 03 44
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
