|
From: | lilypond |
Subject: | Re: Issue 1618 in lilypond: unpredictable placement of rests |
Date: | Sat, 23 Apr 2011 10:38:33 +0000 |
Comment #3 on issue 1618 by percival.music.ca: unpredictable placement of rests
http://code.google.com/p/lilypond/issues/detail?id=1618 I'm happy with this rationale.Another note on valgrind: you _can_ use valgrind on lilypond, but in addition to all the memory errors it finds with guile (I'm not claiming that all these errors are *valid*, merely that valgrind reports errors), it also finds tons of uninitalized variables in guile. If guile was really _that_ full of uninitalized variables, then I can't see how it works at all... but guile clearly _does_ work, so I suspect that valgrind simply doesn't understand how guile sets up variables internally, and thus it's not useful.
Adding suppression files (for example, generating a suppression file from running lilypond with no arguments or files, then using that suppression file when generating the example in question) doesn't help. I only see a few instances of uninitalized variables, but these are all buried deep in the guile library.
[Prev in Thread] | Current Thread | [Next in Thread] |