|
From: | Colin Campbell |
Subject: | Re: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions |
Date: | Sun, 16 Oct 2011 16:56:33 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15 |
On 11-10-16 04:41 PM, Graham Percival wrote:
On Sun, Oct 16, 2011 at 10:08:42PM +0100, Peekay Ex wrote:I still don't really understand them, but while experimenting with values if I use this example with the command lilypond-book --pdfIf you have a segfault, then don't waste time in lilypond-book. Create a Tiny example, and send it to bug-lilypond or add it to the tracker yourself. % this produces a segfault \version "2.15.13" \relative c' { \override Staff.StaffSymbol #'ledger-positions = #'(1) c4 } The bug squad will then enter it as Type-Crash. End of story, no confusion, etc. Cheers, - Graham Added as Issue 1972: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) |
[Prev in Thread] | Current Thread | [Next in Thread] |