[vtk-developers] VTK_DEBUG_LEAKS

[Berk Geveci]

HI David,

> I agree. I mentioned this a while back:
> http://www.vtk.org/pipermail/vtkusers/2009-October/102982.html
>
> Looks like Bill is sticking with his "use valgrind" answer :)
>
> For such an enormous toolkit, though, I'd imagine this functionality
> would be well worth the effort (*cough* next project for ARB's
> consideration? *cough*)

We (the VTK-ITK-ParaView community) are (mostly) focused on developing
analysis and visualization functionality. Even though we put some
effort into making it easy to debug these toolkits, we have no
expertise, interest and time to develop fancier tools for debugging.
That is the specialty of folks that develop VS, Valgrind, gdb etc etc.

Even though I would love to see DebugLeaks have the functionality you
describe, it is not trivial to implement and I don't see it happening.
Unless there is a VTK developer out there who specializes in such
things and has enough interest and time to take on the task :-)

-berk

On Thu, Jan 14, 2010 at 11:11 PM, David Doria <daviddoria+vtk at gmail.com> wrote:
> On Thu, Jan 14, 2010 at 6:02 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> valgrind
>>
>> On Thu, Jan 14, 2010 at 5:50 PM, Arnaud Gelas
>> <arnaud_gelas at hms.harvard.edu> wrote:
>>> Hi Guys,
>>>
>>> I really liked the idea of VTK_DEBUG_LEAKS to know exactly which objects
>>> were not deleted (name of objects forgot to be deleted and number of
>>> instances)
>>> But the way it is right now it is quite difficult to get a clue on WHERE we
>>> forgot to delete (maybe due to the lack of hierarchical information?).
>>>
>>> Is there anyway to improve it by adding some additional information to track
>>> where leaks exactly come from?
>>>
>>> Arnaud
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>
> Arnaud,
>
> I agree. I mentioned this a while back:
> http://www.vtk.org/pipermail/vtkusers/2009-October/102982.html
>
> Looks like Bill is sticking with his "use valgrind" answer :)
>
> For such an enormous toolkit, though, I'd imagine this functionality
> would be well worth the effort (*cough* next project for ARB's
> consideration? *cough*)
>
> Thanks,
>
> David
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>