Knut Petersen <knut_peter...@t-online.de> writes: > Hi Guy! > >> Starting lilypond-windows.exe 2.19.56 >> [Leloupgarou_transformationscene-pianoReduction.ly]... >> >> Processing `[filename].ly' >> >> Parsing... >> >> Interpreting >> music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232] >> >> Preprocessing graphical objects... >> >> Interpreting music... >> >> MIDI output to `[filename].mid'... >> >> Finding the ideal number of pages... >> >> Fitting music on 9 or 10 pages... >> >> Drawing systems... >> >> warning: compressing over-full page by 7.1 staff-spaces >> >> warning: page 3 has been compressed >> >> Exited with return code -1073741819. > > Try to play with set-global-staff-size. > > It's definitely possible to find combinations of global staff size, > page-count, system-count, etc > and music that are hard or impossible to solve. I remember more than > one segfault caused > by such an exercise. That problem is old, it is also reproducible on > linux systems and current > git master.
Uh, the proper way to throw in the towel is not a segfault. If you can find a reproducible manner of segfaulting on a hard page break problem, that warrants fixing. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
