Memory Leak Detection for Windows Mobile 6.1

Question

I'm programming windows mobile application.

I'd like to check memory leak for this application.

I used the following code and _CrtDumpMemoryLeaks() for Windows Application.

 

#define _CRTDBG_MAP_ALLOC

#include <stdlib.h>

#include <crtdbg.h>

 

However, I can't use this code for windows mobile

And there are some compile error.

 

Please, Help me for memory leak detection of Windows Mobile Application.

Answer 1

To test for memory leaks on your Windows Mobile app, you can use the Application Verifier tool. MSDN has good documentation on the tool,

Application Verifier Tool

Application Verifier for Windows CE and Windows Mobile 5

 

Prabhu
www.geekswithblogs.net/techtwaddle

Answer 2

Are you coding in C++

then override new and delete operator and use the counters and log  __FILE,__LINE macro into log files and do code coverage...

 

Hope this works for you..

 

 

Siva.

 

---

-Siva. * Please mark as answer and vote if my post help to fix your issue.*

Answer 3

Thanks for good answer.

 

Isn't there Application Verifier for Windows Mobile 6.0 or 6.1???

 

Thanks in advance.

Answer 4

I'm sorry but I'm coding in C.

 

Thanks.

Answer 5

The Application Verifier tool should work with Windows Mobile 6.0/6.1 as well.

 

Prabhu
www.geekswithblogs.net/techtwaddle

Answer 6

Where can I find the information and document how to apply

this  application to windows mobile 6.0/6.1???

 

Answer 7

Where can I find the information and document how to apply

this  application to windows mobile 6.0/6.1???

 

PrabhuK's second link "Application Verifier for Windows CE and Windows Mobile 5.0" tells you how to use App verifer for Windows Mobile. It is no different to use it on Windows Mobile 5 than it is WM6 or WM6.1.

-PaulH

Answer 8

#define _CRTDBG_MAP_ALLOC

#include <stdlib.h>

#include <crtdbg.h>

However, I can't use this code for windows mobile

And there are some compile error.

There is an upstarting project at SourceForge: <http://sourceforge.net/projects/crtdbg4wince/>.

Currently not implemented all the Features from _CrtDbg for Desktop, but quite helpful for most problems.

Try it out!

Answer 9

you could give _CrtDbg for WinCE a try: 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 have plans to fix this next few days.

It's much easier to use than Appverify...
Greetings to Sue Loh from here: Hi Sue, thank you for the MEDC'2007 talk and introduction of Appverify. I don't want to rant against Appverify & your CeLog here. But sometimes it doesn't resolve the locations for unknown reason. And sometimes I'm tired of explaining Appverify and it's pitfalls to new team mates...

regards,
Modem Man