Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly

[lilypond]

Comment #6 on issue 1031 by hanwenn: constantly-changing  
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031

have you tried running it through valgrind? It might turn up a subtly  
uninitialized
variable issue.

Another thing to look for is places where we sort vector<Foo*> arrays by  
pointer
address. We should probably put deterministically determined numbers (eg.  
enumerate
all grobs using a global counter) in the Grob and use that to sort things.