Paul Hodges <p...@cassland.org> writes: > --On 05 May 2018 17:01 -0700 Aaron Hill <lilyp...@hillvisions.com> > wrote: > >> How about this repro: > > I can confirm that I get the failure with this at the same number of > repetitions. > > I also made a single character change in my sample which reversed the > fault on/off twice, but after that the fault did not return with the > same change... (I recall that being a characteristic when I first hit > the issue). > > So we have a problem which is (1) history dependent, and (2) it seems, > Windows only. I even wonder now wonder if the problem is as deep as a > Python for Windows issue.
Python does not play into it. It's likely GCC and/or Guile related. I think we comparatively recently updated the toolchain used for compiling stuff. Can you try with 2.19.81? It was available at some other download location (our customary location was broken IIRC). -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
