"Phil Holmes" <m...@philholmes.net> writes: > ----- Original Message ----- > From: "Petr Gajdos" <pgaj...@suse.cz> > To: <lilypond-devel@gnu.org> > Sent: Friday, August 09, 2013 11:07 AM > Subject: Re: wrt 'Make doc crashing on my PC' > >> that reason at least on my machine. It seems to me therefore that 2.17.18 >> do not expose the issue but 2.17.19 does. > > > That stacks up well with my earlier investigations. Git besect > identified 35d5f2e2ff40e0bd35cf00f22c2428eac354e566 as the first bad > commit, and that commit occurred between 17.18 and 17.19. That's some > scheme, so I don't understand how it would make the system crash. > > However, I can only get a crash when I run make doc, so wasn't 100% > sure this was really the cause. Also, I believe I tried a revert of > the commit, and it didn't fix it either. I guess it's possible it was > a set of commits that cause the problem.
Well, it's clearly the set of commits centered around issue 3330. Now it would be really a step backwards to revert all that. The problem will occur now because orchestra.ly causes a stencil to be created that is either a) actually defective/inconsistent data b) triggering code unable to deal with all conceivable proper stencils Since the given redefined command is used a _lot_, it would appear that case a) is unlikely to have resulted only in orchestra.ly problems. So I pretty much expect this to be a case of b). -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
