bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: multiple fret-diagram-x markup commands and lilypond safe-mode


From: Reinhold Kainhofer
Subject: Re: multiple fret-diagram-x markup commands and lilypond safe-mode
Date: Sat, 17 Sep 2011 17:48:51 +0200
User-agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.0; i686; ; )

Am Saturday, 17. September 2011, 17:38:48 schrieb Julien Rioux:
> Thanks for testing.
> 
> Interestingly, with your minimal example and guile 1.8.8,
> lilypond s1.ly s2.ly succeeds, but not with the eps backend:

Initially, I could also only reproduce with the eps backend, but now the crash 
appears also with any backend I choose (even with the null backend)...

address@hidden:~/temp/safe-mode-bug$ lilypond -dbackend=null s1.ly s2.ly
GNU LilyPond 2.15.12
»s1.ly« wird verarbeitet
Analysieren...
Ideale Seitenanzahl wird gefunden...
Musik wird auf eine Seite angepasst...
Systeme erstellen...
»s2.ly« wird verarbeitet
Analysieren...
s2.ly:5:21: Fehler: GUILE signalisierte einen Fehler für den hier beginnenden 
Ausdruck
\fret-diagram-terse #
                     "x;x;o;2;3;2;"
Wrong type argument in position 1 (expecting module): #<freed cell 0xb6b7b890; 
GC missed a reference>
/home/reinhold/lilypond/lilypond/out/share/lilypond/current/scm/fret-
diagrams.scm:886:17: In procedure string-split in expression (string-split 
definition-string #\;):
/home/reinhold/lilypond/lilypond/out/share/lilypond/current/scm/fret-
diagrams.scm:886:17: Wrong type argument in position 1 (expecting string): 
#<unspecified>


So, I think we can rule out any backend-cause.

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]