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]
Am Do., 7. Apr. 2022 um 10:41 Uhr schrieb Jean Abou Samra :
> Doesn't reproduce for me.
>
> $ build/out/bin/convert-ly --version
> 2.23.8
> $ ~/lilypond2.23.7/bin/convert-ly --version
> 2.23.7
>
> Are you very sure that the convert-ly you're invoking is from 2.23.7 or
> master?
You're right, I c
> Le 07/04/2022 10:34, Thomas Morley a écrit :
>
>
> Hi,
>
> invoking convert-ly from released 2.23.7 or current master shows a
> wrong version:
>
> $ convert-ly --version
> 2.22.1
>
> Similar for $ convert-ly -h
Doesn't reproduce for me.
$ build/out/bin/convert-ly --version
2.23.8
$ ~/li
Hi,
invoking convert-ly from released 2.23.7 or current master shows a
wrong version:
$ convert-ly --version
2.22.1
Similar for $ convert-ly -h
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/b
