Am Dienstag, 1. Februar 2011, um 00:18:50 schrieb Neil Puttock: > On 31 January 2011 15:37, Reinhold Kainhofer <reinh...@kainhofer.com> wrote: > > Unfortunately, I can't reproduce the problem with current master... I > > tried running valgrind, but I only get some uninitialized variable > > warnings for the usual *mark* functions (I sent a mail to lilypond-devel > > about these, too). > > I can only reproduce it using a GUB binary. > > Looking at part-combine-iterator.cc, the only thing which looks > remotely suspicious is the pair of uninitialized members busy_ and > notice_busy_.
Yeah, that was my first attempt. But since I couldn't reproduce the crash, I have no idea what's the real cause of the crash. Those uninitialized varialbes cause one valgrind warning, but I don't see how they might cause a crash with that backtrace. Anyway, I have now pushed a commit that initialized the variables. Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
