Re: Problems with recent versions of Lilypond

[Chris Sawer]

Mats Bengtsson wrote:
> Anyway, run Lilypond from within a debugger (gdb). When it
> stops with a segmentation fault, issue the command `bt' to 
> get a backtrace of the calling stack and send it to this list.

Thanks very much. I've done that and the following results:

bash-2.03$ gdb lilypond
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(no debugging symbols found)...
(gdb) run volta.ly
Starting program: /usr/local/bin/lilypond volta.ly
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
GNU LilyPond 1.3.150
Now processing: `volta.ly'
Parsing...
Program received signal SIGSEGV, Segmentation fault.
0x400301e7 in ?? () from /usr/local/lib/libguile.so.9
(gdb) bt
#0  0x400301e7 in ?? () from /usr/local/lib/libguile.so.9
#1  0x40030572 in ?? () from /usr/local/lib/libguile.so.9
#2  0x80a14a5 in strcpy ()
#3  0x80a1527 in strcpy ()
#4  0x81026bb in strcpy ()
#5  0x8107609 in strcpy ()
#6  0x80a3097 in strcpy ()
#7  0x80c32a9 in strcpy ()
#8  0x80927ed in strcpy ()
#9  0x40046953 in ?? () from /usr/local/lib/libguile.so.9
#10 0x40049bda in ?? () from /usr/local/lib/libguile.so.9
#11 0x4006aa97 in ?? () from /usr/local/lib/libguile.so.9
#12 0x40049b94 in ?? () from /usr/local/lib/libguile.so.9
#13 0x400498c5 in ?? () from /usr/local/lib/libguile.so.9
#14 0x40046981 in ?? () from /usr/local/lib/libguile.so.9
#15 0x809406d in strcpy ()
#16 0x401042e7 in ?? () from /lib/libc.so.6
(gdb)

I'm slightly puzzled by the "no debugging symbols found"
message - I did compile Lilypond with debugging enabled.

Similar messages to the above appeared when I was using
Guile 1.3.4. I upgraded to 1.4 which as you can see
didn't improve the situation.

Sorry if I'm having to ask at every stage with this, but
I'm not a programmer and debugging is not something I've
had to do before.

Thanks for all the help,

Chris