[vtkusers] vtkDebugLeaks...?

[Andrew Maclean]

Hi Charles,

It works perfectly for me. Are the DLLs compiled with the debug leaks option
on in your path?

You could also consider using:
vtkSmartPointer < vtkActor > pNewActor = vtkSmartPointer < vtkActor
>::New();

This should manage the construction/destruction of the objects
automatically.  

Andrew


-----Original Message-----
From: Charles Boivin [mailto:okeovtk at gmail.com] 
Sent: Wednesday, 25 May 2005 07:20
To: vtkusers at vtk.org
Subject: [vtkusers] vtkDebugLeaks...?

I am re-sending this, as it does not seem it made it through (i.e. I
never received it back as part of the list). Apologies if this is a
duplicate for some.

Hello all,

I am trying to investigate leaks in my library, and I have just
recompiled the VTK binaries with the VTK_DEBUG_LEAKS option activated.
I then set up a test case to see if VTK would catch it..

Here is what I did. In the constructor of my main class, I added this:

vtkActor* pNewActor = vtkActor::New();

And added nothing else to the destructor (on purpose). I expected VTK
to let me know about this one, but again, nothing! I guess I need to
know how to use this vtkDebugLeaks class a bit better...

I am running VTK 4.4 on Windows XP, compiled with VS.NET 2003. What
behavior should I be expecting from vtkDebugLeaks? Is there anything
else that I need to turn on? I am using the libraries compiled in
'Release' mode -- could that be the problem?

Thanks in advance,

Charles Boivin