Knut Petersen <knut_peter...@t-online.de> writes: > Am 29.07.2017 um 09:01 schrieb David Kastrup: >> >> 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. > > I remember segfaults that looked exactly like Guys, but those scores > have changed a lot and I don't > have the old versions. Maybe I find something in old backups. > > One score that reliably segfaults with global staff size above a > certain limit is attached to issue #5169, > but I think that segfault is caused by a different problem.
No idea. This occurs for stuff that fails to have a system assigned for whatever reason while code depends on it. I am trying to figure out right now if it should. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
