[vtk-developers] Valgrind and other dashboard issues

[David Gobbi]

Hi All,

There seem to be some valgrind issues (and dashboard warnings, test
failures) that have been around for a long time.  It used to be the
case that when people submitted code, they were given a stern warning
if their code broke the dashboard, usually Bill Lorensen was the one
cracking the whip.  These days, dashboard issues don't seem to draw
much attention.

For valgrind, specifically, these uninitialized memory
reads/conditionals have been around for ages:

Polyhedron/MVC: 5 UMRs, 1 UMC
ReebGraph:  2 UMRs, 56 UMCs, 1 mismatched deallocate (!!!!)
ZsweepConcavities: 1 UMR, 1 UMC

The responsibility for fixing these issues should be shared between
the person who submitted the code, and the person/group who accepted
the code.  But most importantly, the VTK community as a whole should
be more proactive in chasing after people to get these issues fixed.

This might be an issue for the ARB to discuss.

 - David