Unfortunately I haven't been able to reproduce the error after reverting back to 2.22.0 (the file that caused the error also grew significantly while using the dev-version), but I will recompile lilypond with debug symbols and if I run into something alike again I will look into it and let you know!
All the best Christian Am Fr., 12. Feb. 2021 um 21:03 Uhr schrieb Jean Abou Samra < j...@abou-samra.fr>: > > Le 12/02/2021 à 17:05, Christian Masser a écrit : > > Hi Jean! > > > > I got a similar error two days ago with a pretty basic file, nothing > > fancy at all. (To be precise: changing "des2." to "des2. ~ des" > > produced the error.) > > After switching to the then up-to-date dev-version (from "2.22.0-2" to > > "2.23b30375.2e8c87df0f-1" on arch linux) the error went away. Would > > backtracing it still help you in any way? > > > > All the best > > Christian > > > Hello, > > At any rate, it would be helpful to see the code in question. > Segmentation faults on Linux make bug squashers happy since most of them > (on LilyPond) are running GNU/Linux, so there's at least a slight chance > to reproduce. > > Of course, if you are familiar with the debugger, a backtrace and > whatever information you may get would also help. Be aware that released > binaries (and, I'd bet, your system's package) do not contain debugging > symbols. You'll have to compile LilyPond yourself, see > http://lilypond.org/doc/v2.22/Documentation/contributor/compiling > > Thank you, > Jean > >
