Memory Leak Debugging ( and COM )
Work for a company called Compuware Corporation which specializes in
application software development, testing and management tools. In
particular we have tools that focus to a specific line of code, give an
explanation, and suggest a fix. If interested in learning more, please call
972-577-0293, and visit our website at www.compuware.com.
> I've been using the _CrtDumpMemoryLeaks() and _CrtMemCheckpoint functions
> try and isolate some elusive memory leaks in a multi-process COM/ATL
> project. This doesn't work so well for a few reasons, maybe someone can
> help me out and explain why??
> 1. even though I have the following in my stdafx.h:
> #define _CRTDBG_MAP_ALLOC
> #include <stdlib.h>
> #include <crtdbg.h>
> I still do not get the filename and line number for my memory dumps....
> 2. I am unable to set breakpoints on allocation order numbers. I've
> manually setting them using
> the Watch window and _crtBreakAlloc and also programmatically with
> _CrtSetBreakAlloc( ) but they are just ignored?? ( I have stepped into an
> out-of-process COM object when this happens)
> 3. In some components even my _CrtDumpMemoryLeaks( ) calls are
> I __really__ need to solve this problem...and soon!!! Anyone with
> expertise in this area please throw me a bone!!! Thank you,
> Colin Reinhardt