Re: how to build lilypond in debug mode?

[David Kastrup]

Frédéric Bron <address@hidden> writes:

> Hi,
> I would like to run lilypond in gdb to understand what happens when using 
> ties.
> How can I build lilypond for that?
> When I run configure --help, it says it is built with debug info by default:
> "--enable-debugging      compile with debugging info. Default: on"
> But when I run gdb, I get some strange errors (see below).
> Frédéric
>
> gdb) run toto2.ly
> Starting program:
> /home/fred/lilypond/build-2013-07-25_11-30/lily/out/lilypond toto2.ly
> Traceback (most recent call last):
>   File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3600.3-gdb.py",
> line 9, in <module>
>     from gobject import register
>   File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
>     import gdb.backtrace
> ImportError: No module named backtrace
> Traceback (most recent call last):
>   File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3600.3-gdb.py",
> line 9, in <module>
>     from gobject import register
>   File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
>     import gdb.backtrace
> ImportError: No module named backtrace
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Missing separate debuginfo for /lib64/libgraphite2.so.3
> Try: yum --disablerepo='*' --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/a1/aa32c91bc181cb69ebc81bbfd03a1349ea4e33.debug

All that looks unrelated to LilyPond and more like a buggy installation
of gdb

> GNU LilyPond 2.17.23
> warning: not relocating, no 2.17.23/ or current/ found under
> /home/fred/lilypond/build-2013-07-25_11-30/lily/share/lilypond/
> ERROR: In procedure primitive-load-path:
> ERROR: Unable to find file "lily.scm" in load path
> [Inferior 1 (process 9056) exited with code 01]

And that one's
<URL:http://sourceware.org/bugzilla/show_bug.cgi?id=15415>

You can get around it by doing
break main
run toto.ly
set argv[0] = "/home/fred/lilypond/build-2013-07-25_11-30/out/bin/lilypond"
continue

Or by doing
ln -f /home/fred/lilypond/build-2013-07-25_11-30/{lily/out/lilypond,out/bin}

But remember to do this after _every_ recompilation or you'll get the
old binary in out/bin until the next "make clean".

> Missing separate debuginfos, use: debuginfo-install
> compat-guile18-1.8.8-6.fc19.x86_64 expat-2.1.0-5.fc19.x86_64
> fontconfig-2.10.93-1.fc19.x86_64 freetype-2.4.11-6.fc19.x86_64
> glib2-2.36.3-2.fc19.x86_64 glibc-2.17-11.fc19.x86_64
> gmp-5.1.1-2.fc19.x86_64 harfbuzz-0.9.18-3.fc19.x86_64
> libffi-3.0.13-4.fc19.x86_64 libgcc-4.8.1-1.fc19.x86_64
> libstdc++-4.8.1-1.fc19.x86_64 libtool-ltdl-2.4.2-16.fc19.x86_64
> nss-softokn-freebl-3.15.1-1.fc19.x86_64 pango-1.34.1-1.fc19.x86_64

All those are nice to have, but not essential to debugging LilyPond but
rather stuff in its included libraries.

-- 
David Kastrup