Memory Leak Detection in Windows Mobile 6 using <crtdbg.h>, How ??
Goel@discussions.microsoft.com Pulkit Goel
I am Using Visual Studio 2005, In "Windows Mobile 6 Application Development"
In my VC++ Programme there is some Memory Leak Problems..,
so, i find there is many helpful function like "_CrtDbgBreak" ,but in
Windows mobile 6, there is no header file of name like <crtdbg.h>, so, How i
include this header file in my source code.. or there is any other method of
debugging/finding memory leaks..
r_z_...@pen_fact.com
I just used google (http://groups.google.com/advanced_search?q=&) to
look up
memory leak
in this newsgroup and got 170 hits. I took a quick look and am quite
sure at least some were relevant and useful.
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com
mike
operator new & new[] that I need for debuging. It is not include in any of
the sdk's I have, including a CePc one i built using platform builder & ce6.0
to try and get an x86 copy of the file.
It is included under
C:\WINCE600\PRIVATE\WINCEOS\COREOS\CORE\CORELIBC\CRTW32\H
(my ce install root, obviously)
but even when, as above, i make a new platform build and select every option
even sounding like debug, it is not included in the os or sdk...
On desktop windows, this file is very large, while in the ce6.0 source it is
short, basically a pass-through to cruntime.h which itself basically just
includes windows.h and stdlib.h ...
PLEASE HELP!!! I honestly have no idea why this file doesn't go in the
image, and I have searched msdn & google quite a bit w/ no results - not even
an admonition it is not supported, etc...
Sergeant Kolja
> ... in Windows mobile 6, there is no header file of name like <crtdbg.h> ...
you could give _CrtDbg for WinCE a try: <http://sourceforge.net/projects/crtdbg4wince/>
It is under active development and stated to be Alpha, but it can already find all your malloc, callor, realloc, strdup, new, new [] leaks.
Aside of this, it also finds leaked CreateFile handles and more. "alpha" state is not because of lack of reliability, it's just because it not yet resembles all sophisticated commands of the original _CrtDbg API. It also need to be removed the .h and .cpp file from project for release build, but I got the message this will be done next few days.