lilypond-devel
[Top][All Lists]
Advanced

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

Re: signal 11 strack trace(?)


From: Juergen Reuter
Subject: Re: signal 11 strack trace(?)
Date: Wed, 18 Feb 2004 00:39:17 +0100 (CET)


On Tue, 17 Feb 2004, David Bobroff wrote:

> (no debugging symbols found)...(no debugging symbols found)...

When compiling lily, you should pass option

--enable-debugging

to ./autogen.sh or ./configure (whatever you use) to keep debugging 
symbols in lilypond-bin.  Similarly, if you compile guile by yourself, it 
may a good idea to turn on debugging symbols on it as well.

> (gdb)

Do not forget to load the core dump file into gdb, e.g.

(gdb) core core.7125

If your shell does not produce a core dump file in the current 
directory (it should say something like "Signal 11 (core dumped)" or 
similar), then you probably have the core dump limit set wrong.  I 
recommend to set it to at least 15 MByte (e.g. by "limit core 15M" in 
tcsh; in bash the command is called "ulimit").  After loading the core 
file into gdb, try:

(gdb) bt full

to produce a full backtrace.


Jan / Han-Wen:  On the current lilypond site, is there somewhere a guide 
how to report bugs?  If yes, it's well hidden, as I could not immediately 
find it.  If no, the above description or something similar should be 
added.


Greetings,
Juergen




reply via email to

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