Przemysław Pawełczyk <przemoc <at> gmail.com> writes:
I've provided some more information at:
GNU LilyPond 2.15.27 - segfault
GNU LilyPond 2.15.28 - ok
GNU LilyPond 2.15.29 - ok
GNU LilyPond 2.15.30 - segfault
BTW I'm using 64-bit releases, forgot to mention it before.
I cannot reproduce this either,
on Windows 32-bit, version 2.15.27, with or without redirection
of LilyPond's messages to a file.
Przemoc's example is not very long, but it involves lots of features.
It would be good for anyone using a 64 bit system to try to reproduce
the segfault (emergency early-stopping of LilyPond) and even better
to start reducing the example to isolate the troublesome feature,