I had the same problem. 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.
Greetings,
Sarge
Post by fantasy1215 via PocketPCJunkies.comI notice there's no <crtdbg.h> under Wince5.0 sdk,
So How do you detect memory leaks, guys?
Or is there some articles express detecting memory leaks under wince?
--
Message posted via http://www.pocketpcjunkies.com
Post by Paul G. Tobey [eMVP]I don't know about articles. There are commercial programs that do this
from ENTREK. There's also the Application Verifier from Microsoft, which
should be in the Tools menu in Platform Builder, if you are the one building
the device.
Paul T.