I got a different stack trace than the other one posted. I got:
-------------------------------------------
(gdb) run
Starting program: /usr/bin/lilypond
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x401604de in __libc_free (mem=0xbfffd418) at malloc.c:2921
(gdb) bt
#0 0x401604de in __libc_free (mem=0xbfffd418) at malloc.c:2921
#1 0x400daf6e in __builtin_delete (ptr=0xbfffd418)
#2 0x8183058 in __dynamic_cast ()
#3 0x8158cb3 in __dynamic_cast ()
#4 0x815daac in __dynamic_cast ()
#5 0x80de0c2 in __dynamic_cast ()
#6 0x810a22b in __dynamic_cast ()
#7 0x80c7fc8 in __dynamic_cast ()
#8 0x40044c4d in gh_launch_pad ()
#9 0x400472a9 in invoke_main_func ()
#10 0x4006c71b in scm_internal_lazy_catch ()
#11 0x4004725b in scm_boot_guile_1 ()
#12 0x40046ff9 in scm_boot_guile ()
#13 0x40044c88 in gh_enter ()
#14 0x80c8ad8 in __dynamic_cast ()
#15 0x4011fcb3 in __libc_start_main (main=0x80c8540 <__dynamic_cast+516828>,
argc=1, argv=0xbffff824, init=0x8049b84 <_init>, fini=0x819aacc <_fini>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff81c)
at ../sysdeps/generic/libc-start.c:78
-------------------------------------------
...which looks pretty ugly to me :). This was just "gdb lilypond".
I also discovered I have libstdc++, but not the "devel" one, in case
that helps.
Does the stack trace mean that there's probably a bug in something
else such as libc, and I need to wait for another libc?
:)
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [EMAIL PROTECTED] | I am |
---------------------------------------------------------------------
Web: http://www.ne.com.au/~wayland/
NB: I have a BSc. (Comp.Sci.) and I need a Job
----BEGIN GEEK CODE BLOCK----
Version 3.1
GCS d? s: a-- C++>++++$ US+ P++ L++ E- W+++ N+ w+> M-- V- Y+>++
PGP->++ R(+) !tv B++ DI++++ D+ G e>++ h!/* y-
-----END GEEK CODE BLOCK-----
