Re: [Plib-devel] Memory leaks, was: GL_COLOR_MATERIAL pitfall

[Eero P. <epa...@ko...>]

Wolfram Kuss wrote:
> 
> Dave wrote:
> 
> >I spotted a couple leaks in ssgImageLoader.  But I think they only occur
> >when the load fails and the default texture is used.
> 
> Ok, thanks, I will ignore them.
> 
> But at the moment I am still fighting MSVC
> (Microsoft Visual C++) :-(.
> The normal way to search for memory leaks with MSVC is very tedious.
> MSVC tells you all the memory leaks, but it only gives you the index
> of the allocation. So, for example, it says, the things that were
> allocated 6. and 23. of all allocations were not freed until the
> termination of the program.
> Of course it would be much better if you could convince MSVC to
> tell you where (filename + linenumber) the allocations were, but this
> is very difficult to achieve :-(.
> 

On Windows (and on Unix when Purify was not available).
I have used the Boehm garbage collecting malloc
library as a leak detector. It is usefull
because it only complains from leaked memory areas.
It doesn't complain just because you don't free
those areas which you allocate in the begining, and use to
the end of program run. 





In addition to the gc-malloc there are tools like
heapagent, which you might request for evaluation...



		Eero