Comment #4 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I would simplify it if I knew how to do it preserving the segfault. :)
Summary of tests performed using 64-bit LilyPonds in Debian Wheezy x64 (as
it should be here too for convenience).
GNU LilyPond 2.14.2 - warnings
GNU LilyPond 2.15.0 - warnings
GNU LilyPond 2.15.1 - warnings
GNU LilyPond 2.15.2 - warnings
GNU LilyPond 2.15.3 - warnings
GNU LilyPond 2.15.4 - warnings
GNU LilyPond 2.15.5 - warnings
GNU LilyPond 2.15.6 - warnings
GNU LilyPond 2.15.7 - warnings
GNU LilyPond 2.15.8 - warnings
GNU LilyPond 2.15.9 - warnings
GNU LilyPond 2.15.10 - warnings
GNU LilyPond 2.15.11 - ok
GNU LilyPond 2.15.12 - ok
GNU LilyPond 2.15.13 - ok
GNU LilyPond 2.15.14 - ok
GNU LilyPond 2.15.15 - ok
GNU LilyPond 2.15.16 - ok
GNU LilyPond 2.15.17 - ok
GNU LilyPond 2.15.18 - ok
GNU LilyPond 2.15.19 - ok
GNU LilyPond 2.15.20 - ok
GNU LilyPond 2.15.21 - ok
GNU LilyPond 2.15.22 - ok
GNU LilyPond 2.15.23 - segfault
GNU LilyPond 2.15.24 - segfault
GNU LilyPond 2.15.25 - segfault
GNU LilyPond 2.15.26 - segfault
GNU LilyPond 2.15.27 - segfault
GNU LilyPond 2.15.28 - ok
GNU LilyPond 2.15.29 - ok
GNU LilyPond 2.15.30 - segfault
Actually removing resetRelativeOctave was tested and it still segfaulted.
Removing articulate was "too much" though and there was no segfault then.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond