[vtkusers] memory-related problem detected using Valgrind

[David Cole]

Valgrind is run nightly on "dash6.kitware" on the VTK dashboards.

Here are last night's results:
http://www.vtk.org/Testing/Sites/dash6.kitware/Linux-g++/20080204-0300-Nightly/DynamicAnalysis.html

While there are a handful of tests that show some problems on this valgrind
run, this is the result of running more than 600 test programs as part of
the nightly dashboard on that machine. And when you dig into these, you will
often encounter valgrind identifying issues in non-VTK code (XWindows
implementation shared libs, Mesa shared libs, others)

If you could pinpoint the uninitialized value and demonstrate that it comes
from someplace in the VTK source tree, I'd be happy to correct it and commit
a fix to the VTK code.


Thanks,
David Cole
Kitware, Inc.


On 2/4/08, Marie-Gabrielle Vallet <mgv.research at gmail.com> wrote:
>
> I believed I had a memory-related problem with my vtk code. I ran it through
> Valgrind, a memory checking program. It detects some problems :
>   Conditional jump or move depends on uninitialised value(s)
>   Use of uninitialised value of size 8
>   Invalid read of size 8
>
> BUT, running Valgrind on the very simple following code results in the
> same messages... that's disturbing!
>
> Has someone ever checked any vtk software for such flaws ?
>
> Marie-Gabrielle Vallet
>
> _______________________________________________
> This is the private VTK discussion list.
> Please keep messages on-topic. Check the FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20080204/47198db0/attachment.htm>