Thank you for your quick response! I tried Lilypond 2.20 now on Windows and Linux and the segfault disappeared. Sorry for the false alarm. I did not try 2.20 in the first place, because I did not find any bug report and thought that the error appears under such specific circumstances that it is unlikely to be discovered. But apparently, it was fixed!
Just in case you are still interested, here is the Lilypond 2.18 output: $ lilypond bugreport.ly GNU LilyPond 2.18.2 Processing `bugreport.ly' Parsing... Interpreting music... Preprocessing graphical objects...Segmentation fault (core dumped) Best, Mathias -----Original Message----- From: Federico Bruni <f...@inventati.org> Sent: 06 March 2020 16:34 To: Mathias Bockwoldt <mathias.bockwo...@uit.no> Cc: bug-lilypond@gnu.org Subject: Re: Segfault when using specific symbol combination Il giorno ven 6 mar 2020 alle 11:38, Mathias Bockwoldt <mathias.bockwo...@uit.no> ha scritto: > Dear Lilypond team, > > I found a symbol combination that triggers a segfault in Lilypond > 2.18.2 on Linux (Linux subsystem for Windows 10). I did not have the > chance to reproduce on other machines or with other versions. > I tried looking for the bug in the database and I am 98% sure that it > is not there, yet. > More information about the actual circumstances for the bug is in the > attached file. > > Thank you for this great product! > Mathias > Can you paste lilypond output here? I cannot reproduce it using "native" Linux and lilypond 2.20. Your example compiles without errors. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
