On Mon, Jan 31, 2011 at 11:52 AM, Reinhold Kainhofer <[email protected]> wrote: > Due to the crash with the part-combiner (which I cannot reproduce, > unfortunately), I'm currently taking a closer look at lilypond with valgrind. > > 1) Somehow the Rhythmic_head interface generates a "Conditional jump or move > depends on uninitialised value(s)" warning (none of the other ADD_INTERFACE > calls does, only Rhythmic_head): > > I fail to see any different to other interfaces, which do not trigger such a > warning. Any idea what might be wrong here? > > > 2) The example for the 2.13.47 crash posted to the bug list does not crash > here, but running it through valgrind shows a lot of warnings like the > following: > > All of them have in common, that ly_music_length (or ly_moment_mul) and > Moment::smobbed_copy are called and then the condition on the uninitialized > value happens in scm_gc_mark function. > > Unfortunately, I'm unable to find out from where these are called, as it > happens from scheme apparently, and valgrind does not provide any useful > information about scheme calls... > > Any idea how to find out the offending code / moments?
[snip] I have seen these errors before a few years ago, and have spent many hours trying to hunt them down, to no avail. Maybe it's best to just give up. -- Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
