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

[Dave M. <Dav...@dy...>]

I recommend using "NuMega BoundsChecker" with Visual C++.
If you go to:

http://www.numega.com/devcenter/bc.shtml

and click on the "Try It!" button on the left-hand frame
you can get an eval copy.  BoundsChecker tells you exactly
where in the source code the memory leaks are occuring.

--Dave

> -----Original Message-----
> From: pli...@li...
> [mailto:pli...@li...]On Behalf Of 
> Wolfram Kuss
> Sent: Sunday, April 30, 2000 1:44 PM
> To: pli...@li...
> Subject: [Plib-devel] Memory leaks, was: GL_COLOR_MATERIAL pitfall
> 
> 
> 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 :-(.
> 
> Just out of curiosity, are there tools to look for memory leaks under
> Linux?
> 
> At the moment I can only say that a lot of memory blocks are leaked if
> I just start PPE and close it right away.
> 
> 
> Bye bye
> Wolfram
> 
> _______________________________________________
> plib-devel mailing list
> pli...@li...
> http://lists.sourceforge.net/mailman/listinfo/plib-devel
>