Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Carl Sorensen
On 2/17/21, 12:21 PM, "Arusekk" wrote: > This statement seems a little bit strange to me. I didn't think we had a > lilypond editing app on Linux -- only on Windows and MacOS. How are you > using lilypond when it is "not told to lay out"? Are you using > Frescobaldi? Are

Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Arusekk
Dnia środa, 17 lutego 2021 20:15:22 CET Jonas Hahnfeld pisze: > Patch up at https://gitlab.com/lilypond/lilypond/-/merge_requests/655 , > this makes the given example work under Asan on my system. It would be > great if you could test on your end (as far as I understand, you > already compiled

Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Arusekk
> This statement seems a little bit strange to me. I didn't think we had a > lilypond editing app on Linux -- only on Windows and MacOS. How are you > using lilypond when it is "not told to lay out"? Are you using > Frescobaldi? Are you using Denemo? Are you using Emacs? I would be >

Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Jonas Hahnfeld via bug-lilypond
Am Mittwoch, dem 17.02.2021 um 18:16 +0100 schrieb Jonas Hahnfeld via bug-lilypond: > Am Mittwoch, dem 17.02.2021 um 00:00 +0100 schrieb Arusekk: > > W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze: > > > Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet), > > > so you'll

Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Carl Sorensen
On 2/16/21, 4:00 PM, "Arusekk" wrote: On my box lilypond crashes every single time I command it to produce PDFs (never does if not told to lay out), so I think I can provide much help, maybe core files, or recorded execution from GDB (never tried to do it before, though).

Re: Lilypond 2.23.0 crashes on layout

2021-02-17 Thread Jonas Hahnfeld via bug-lilypond
Am Mittwoch, dem 17.02.2021 um 00:00 +0100 schrieb Arusekk: > W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze: > > Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet), > > so you'll definitely see worse performance (mostly slower startup) and > > might run into occasional issues,