I appreciate this is going back a whole 9 months, but I've just started looking again at one of my projects and I'm back, stuck against this completely debilitating bug.
I'm now using 2.19.80 and it's not been fixed. Granted, a release build probably wouldn't throw on "assert", but is anyone planning to look at this issue? On Sat, 7 Jan 2017 at 18:50 Chris Yate <chrisy...@gmail.com> wrote: > On Fri, 6 Jan 2017 at 12:41 Chris Yate <chrisy...@gmail.com> wrote: > >> On Fri, 6 Jan 2017 at 12:23 Thomas Morley <thomasmorle...@gmail.com> >> wrote: >> >> 2017-01-06 13:10 GMT+01:00 Chris Yate <chrisy...@gmail.com>: >> >> > >> > Curiously, this didn't fail with assertions. I've just upgraded to >> 2.19.54, >> > and the test cases that crashed for me previously still crash :) >> > >> > Log attached (although I don't think this will be very helpful). >> >> >> >> Strange that your log file (I assume default loglevel) differs >> significantely from mine. >> Seems the order what is done at which time is very different. >> >> > Hi Thomas, > > I've attached the console output from running each of these tests > separately (as individual files and in separate executions of Lilypond). > > I had to separate them out; otherwise the assertions don't crash the > program but only abort the score they occur in. > > I don't know whether this tells you anything more? > > thanks, > > > Chris > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
