GDB giving immediate segfault on LilyPond startup?

[Jean Abou Samra]

Hi,

After upgrading to Ubuntu 22.04 LTS, I can no longer use GDB
with LilyPond, although it runs fine outside of GDB.


$ gdb out/bin/lilypond
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Breakpoint 1 at 0x102530: programming_error. (3 locations)
Breakpoint 2 at 0x102530: file 
/home/jean/repos/lilypond/lily/diagnostics.cc, line 35.
Load new symbol table from "out/bin/lilypond"? (y or n) y
Reading symbols from out/bin/lilypond...
(gdb) run ../input/regression/clefs.ly
Starting program: 
/home/jean/repos/lilypond/build-guile2/out/bin/lilypond 
../input/regression/clefs.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
GNU LilyPond 2.23.9 (running Guile 2.2)

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7cf08f2 in GC_find_limit_with_bound () from 
/lib/x86_64-linux-gnu/libgc.so.1
(gdb) backtrace
#0  0x00007ffff7cf08f2 in GC_find_limit_with_bound () at 
/lib/x86_64-linux-gnu/libgc.so.1
#1  0x00007ffff7cf09da in GC_init_linux_data_start () at 
/lib/x86_64-linux-gnu/libgc.so.1
#2  0x00007ffff7cf1f67 in GC_init () at /lib/x86_64-linux-gnu/libgc.so.1
#3  0x00007ffff7d9bf84 in  () at /lib/x86_64-linux-gnu/libguile-2.2.so.1
#4  0x00007ffff7df1d8f in  () at /lib/x86_64-linux-gnu/libguile-2.2.so.1
#5  0x00007ffff7df2156 in  () at /lib/x86_64-linux-gnu/libguile-2.2.so.1
#6  0x00007ffff7cf080b in GC_call_with_stack_base () at 
/lib/x86_64-linux-gnu/libgc.so.1
#7  0x00007ffff7dec5fc in scm_with_guile () at 
/lib/x86_64-linux-gnu/libguile-2.2.so.1
#8  0x00007ffff7d9be89 in scm_boot_guile () at 
/lib/x86_64-linux-gnu/libguile-2.2.so.1
#9  0x000055555559e9a0 in main(int, char**) (argc=2, argv=0x7fffffffdcc8)
    at /home/jean/repos/lilypond/lily/main.cc:840
(gdb)


This is with Guile 2.2 from the system. It also happens
with self-compiled Guile master (I recompiled it after
the upgrade).

Any clue?

Thanks,
Jean