On 7/23/16 3:29 PM, "Chris Yate" <[email protected]> wrote:
>Hi Carl,
>I get your point, and I do understand the problem with reproducing bugs.
>
>
>With a bit of experimentation, I've got it down to this:
>
>
>---------------
>\version "2.19.45"
>
>
>\score
>{
> <<
> \autoPageBreaksOff
> \time 6/8
> \repeat unfold 18 s2.
> >>
> \header {}
> \layout { }
>}
I got the same thing, once I discovered that I could see the assertion
failure on OS/X, even though it doesn't appear on LilyDev (where I do my
development).
>
>I think if I were trying to diagnose a problem like this I'd want to see
>some really verbose logging. Is there any command line switch I can pass
>to Lilypond to get that output?
You can use -l DEBUG (or --loglevel=DEBUG).
See the Usage manual for information on command line switches:
http://lilypond.org/doc/v2.18/Documentation/usage/command_002dline-usage
HTH,
Carl
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
