RE: Lilypond bug "Exited with return code-1073741819" & workaround

[mclaren]

Andrew --

Thanks for the suggestion about "minimal working examples."

I'm a little puzzled about how I can reduce the size of my Lilpond code. In
the example above, for instance, I need at least one full measure of those
broken tuplets because anything less doesn't get the numerator and
denominator big enough to crash Lilypond.

I included a bunch of different measures merely to show that my workaround
does, indeed, generate measures that pass Lilypond's bar checks, so my
workaround lets the Lilypond effectively get very large time signatures even
though Lilypond won't allow them. 

Thanks for your suggestion about MWEs. I will endeavour to reduce my
examples to smaller amounts of code in future. But not sure in all cases
it's practical, as in many instances I need multiple measures to show
spacing problems, failure of line breaks, etc.

Thanks to Urs Liska & Andrew Ho I think I've gotten Lilypond to force page
breaks now, so that should be less of an issue in the examples I post.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Lilypond-bug-Exited-with-return-code-1073741819-workaround-tp196195p196199.html
Sent from the User mailing list archive at Nabble.com.