It must be a problem with some lib file that's used by LilyPond.
It doesn't call any external application at that spot in the
processing.
Anyway, since nobody else has recognized the problem, it seems to
be something specific for your setup and I'm afraid you have to do
some debugging yourself. Just run the program from within gdb, run
the command "backtrace" when you get to the segmentation fault and
send the resulting output to the mailing list if you cannot figure
it out yourself.
/Mats
Villum Sejersen wrote:
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.
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
