bug reports for valgrind warnings?

[Reinhold Kainhofer]

I let valgrind run lilypond (both with optimization turned on and off) on all 
our regtests, and some of them (3-4) showed some warnings like invalid read 
access or uninitialized values. 

Shall I open a bug report for each regtest where valgrind shows a warning (the 
guile GC warnings are of course filtered out using a suppressions file)?

Some might really point to bugs (like the uninitialized variables that I fixed 
yesterday) or even to heisenbugs (which are not possible to track down, the 
more you narrow the area of the bug, the less you can reproduce it - you know, 
Heisenberg's uncertainty principle).

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, 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