Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Tue, 3 Jun 2008 19:28:47 -0400,    group: microsoft.public.vstudio.development        back       


Weird debug memory report message   
I'm trying to locate a memory leak.  When I request a debug memory report at 
the end of my program, I get these messages:

Detected memory leaks!
Dumping objects ->
{105} normal block at 0x003F6AF0, 5 bytes long.
 Data: <I4 0 > 49 34 20 30 00
Object dump complete.

I noticed I was missing an include of crtdbg in a source file so I added:

#include <crtdbg.h>

Now I get these messages:

Detected memory leaks!
Dumping objects ->
#File Error#(700) : {105} normal block at 0x003F6AF0, 5 bytes long.
 Data: <I4 0 > 49 34 20 30 00
Object dump complete.

Can anyone tell me what I'm doing wrong and how to get the actual file name?

Thanks.

David Liebtag
date: Tue, 3 Jun 2008 19:28:47 -0400   author:   David Liebtag

Re: Weird debug memory report message   
I found the problem.

The routine that allocates the storage is in a dll that is manually loaded 
by our program; there is no reference from our executable to the dll.

When I added a reference from our executable to the dll, the debug memory 
leak message included the source code file name.

Is there a way to get the debug memory facilities to correctly report leaks 
in dynamically loaded dlls?

Thanks a lot.

David Liebtag
date: Wed, 4 Jun 2008 15:59:25 -0400   author:   David Liebtag

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us