2017-07-29 9:53 GMT+02:00 Knut Petersen <knut_peter...@t-online.de>: > 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. > > Knut
Confirmed segfault for this score on Ubuntu 16.04 64-bit with LilyPond 2.19.65, Pity I can't test with 2.18.2 and before because you frequently used new features like fis8. 16 8 Btw, undertie _is_ implemented in the source. Cheers, Harm _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
