Re: GDB giving immediate segfault on LilyPond startup?

2022-05-18 Thread Luca Fascione
On Wed, May 18, 2022 at 9:59 PM Jean Abou Samra wrote: > Le 18/05/2022 à 13:54, Luca Fascione a écrit : > > > > Quoting from that page: > > [...] > > The collector will call abort if the signal > > had another cause, and there was not other handler previously > > installed. > > >

Re: GDB giving immediate segfault on LilyPond startup?

2022-05-18 Thread Jean Abou Samra
Le 18/05/2022 à 13:54, Luca Fascione a écrit : While trying to see if I could help out Jean, I found this piece of documentation about libgc: https://github.com/ivmai/bdwgc/blob/master/doc/debugging.md BDWGC is the project name for libgc.so Quoting from that page: If the fault occurred

Re: GDB giving immediate segfault on LilyPond startup?

2022-05-18 Thread Luca Fascione
While trying to see if I could help out Jean, I found this piece of documentation about libgc: https://github.com/ivmai/bdwgc/blob/master/doc/debugging.md BDWGC is the project name for libgc.so Quoting from that page: If the fault occurred in GC_find_limit, or with incremental collection >

Re: GDB giving immediate segfault on LilyPond startup?

2022-05-17 Thread Jean Abou Samra
Le 17/05/2022 à 13:06, Jean Abou Samra a écrit : Hi, After upgrading to Ubuntu 22.04 LTS, I can no longer use GDB with LilyPond, although it runs fine outside of GDB. [...] Thanks to private replies, I have learnt that this is apparently expected, and it works to type "continue" when

GDB giving immediate segfault on LilyPond startup?

2022-05-17 Thread 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