Le 07/04/2022 à 21:17, Mats Bengtsson a écrit :
(If I add the missing \! in the second ending the file no longer
triggers the SIGSEGV, but I guess that's more of a coincidence).
It actually isn't. This bug was already fixed, see
https://gitlab.com/lilypond/lilypond/-/issues/6219
Best,
Hi,
The following example results in a segfault almost every time I process
it using the 64bit Linux version of 2.23.7, downloaded from
lilypond.org.
The log output is
GNU LilyPond 2.23.7 (running Guile 2.2)
Processing `test1.ly'
Parsing...
Interpreting music...[8][16]
