Re: Issue 1618 in lilypond: unpredictable placement of rests

[lilypond]

Comment #1 on issue 1618 by percival.music.ca: unpredictable placement of  
rests
http://code.google.com/p/lilypond/issues/detail?id=1618

I think it happened earlier than 2.13.48 -- maybe even before 2.12 or 2.10,  
meaning that it's not Critical.  I tried to do a bisect, but I ended up  
looking at a doc translation merge that had nothing to do with code at all!

It's really unfortunate that we can't run valgrind on lilypond; it's great  
for finding the use of uninitalized variables.  Does anybody have any other  
favorite static code analysis tool which can identify uninitalized  
variables?
(the alternative is to spend half an hour seriously looking at variables in  
the relevant part of the source code; I may give that a shot if nobody has  
any other suggestions before tomorrow)