Yes. Sorry for not explaining properly.
Let me put it this way.
I wanted to know about the memory leaks in my application.
I for one know from experience know that if we build the library with debug leaks flag on, we can get the memory leaks present when application is closed.
Earlier I used to work in Linux environment and this process was working great.
But now as I switched to windows using visual studio to build the application and run code using visual studio. I’m facing this issue that when the close the application, I couldn’t get the debug leaks printed.
When I run the application as a console application, using a small project I’m able to get the magic statement… “vtk. has no debug leaks!” .it’s good till this.
But when I try to run my entire project. " which is contributed by many developers like me", the debug leaks are not printed on closing the application and not even the statement that no leaks are there.
So I was wondering if there is any problem with the way visual studio is configured for this particular project or any vtk functions/classes /parameters are blocking this debug leaks to print when application is closed.
So I’m back to this forum to know if there are any such methods/classes which in fact is mistakenly used and there by resulting in hiding the memory leaks.
Hope I explained clearly this time.
Thanks in advance…