crimsonsunr...@protonmail.com writes:
>> crimsonsunr...@protonmail.com writes:
>>
>>> This is pretty much the same error I reported last time with
>>> 2.21.0. This time however, the same error happens on verbose
>>> output. This happens:
> Ativo 9 de jun de 2018 17:44, David Kastrup escreveu:
>>
Mensagem Original
Ativo 9 de jun de 2018 17:44, David Kastrup escreveu:
crimsonsunr...@protonmail.com writes:
> This is pretty much the same error I reported last time with
> 2.21.0. This time however, the same error happens on verbose
> output. This happens:
Do you use any rot
crimsonsunr...@protonmail.com writes:
> This is pretty much the same error I reported last time with
> 2.21.0. This time however, the same error happens on verbose
> output. This happens:
Do you use any rotated stencils? I'm reviewing recent C++ code
contributions and have found a GC error in ro
Mensagem Original
Ativo 9 de jun de 2018 17:21, Thomas Morley escreveu:
2018-06-09 22:00 GMT+02:00 :
> This is pretty much the same error I reported last time with 2.21.0.
So the replies will likely be pretty much the same ;)
Did you try gdb as described
http://lilypond.1069038
2018-06-09 22:00 GMT+02:00 :
> This is pretty much the same error I reported last time with 2.21.0.
So the replies will likely be pretty much the same ;)
Did you try gdb as described
http://lilypond.1069038.n5.nabble.com/Strange-error-with-no-traceable-cause-tp213613p213620.html
(and folow up)?
This is pretty much the same error I reported last time with 2.21.0. This time
however, the same error happens on verbose output. This happens:
Starting lilypond 2.21.0 [score with parts.ly]...
Log level set to 287
Relocation: is absolute: argv0=/usr/bin/lilypond
PATH=/usr/bin (prepend)
Setti
