Virtual Developer Workshop: Containerized Development with Docker

Environment: winCE


This code detects memory leaks in embedded VC++ almost the same way crtdbg does in VC++. At the end of program execution it will display in the debug window if there were any memory leaks and how the memory looks so you can identify where your memory leak occurred. It will display in the debug window a message saying no memory leaks detected if there are no memory leaks. In addition it displays the ammount of free store memory that your program uses.

The code detects memory leaks generated with calls to new and delete operators in C++. The code doesn't detect memory leaks generated with C functions: malloc, calloc, free, but that can be done in the future. Let me know and I will program it.

There are 3 simple steps in order to enable memory leak detection:
  1. Define _DEBUG
          #define _DEBUG
  2. Include "crtdbg.h"
          #include "crtdbg.h"
  3. Let your first line in the code be:
          _CrtSetDbgFlag (ON);

Tips on debugging:

Tip 1:

Although it doesn't display the line where the memory leak occurred (read Tip 2), the utility display the address in hex, and you can add a small code to the operator new function, just after the malloc

if (retPtr == (void*)0x76DA0)
   dumb instruction; <- place a breakpoint on 
                        this one, or just use DebugMsg

so you can detect easily which line of your code called the operator new to allocate memory at the specified address and wasn't freed.

Tip 2:

Here's a trick that allow you to get the correct line and filename where the memory leak occurred. Define the following line in every file, or define it in a header file and include it in every file where you want accurate line and filename:

#define new new(_T(__FILE__), __LINE__)

How it works

What the code actually does is override the global operator new that besides allocating memory, it retains the pointer to the allocated memory in a list. The operator delete simply releases memory and deletes the reference to that memory from the list. In the end of the program execution, all the pointers still in the list simply mean memory leaks, and they are displayed in the debug window.

The macro _CrtSetDbgFlag (ON); simply declares an instance of garbageCollector. It has to be the first line of your code, to insure it is the last variable in your program to be destroy, as in its destructor it performs checking of the pointer list and it displays memory leaks. So its destructor must be the last destructor called. Remember this when you have static variables; you must give a global scope to the instance of garbageCollector. You can do that by placing the macro at the global scope. However, the C++ standard does not provide an order of initialization for static variables, which means you cannot assure garbageCollector will be initialized first. Therefore in case of static or global variables, it will report memory leaks for variables initialized after garbageCollector has been initialized.


Please report any bugs or feedback to Ciprian_Miclaus@yahoo.com.


Download demo project - 11 Kb
Download source - 2 Kb


  • Memory leaks detection tool

    Posted by Petruha on 11/25/2009 07:12pm

    The easiest way is to use some memory leaks detection tool, like Deleaker ( http://deleaker.com/ )

  • Detect meory leak in evc++ due to malooc,calloc and free

    Posted by Legacy on 04/14/2003 07:00am

    Originally posted by: Amoli

    Can someone tell me where I can find the some code similar to this to detect meory leak in evc++ due to malloc,calloc and free as well ?

  • Any Development Tools to Recommend for programming in WinCE??

    Posted by Legacy on 09/19/2002 07:00am

    Originally posted by: bloon

    Anyone here knows any Development Tools to Recommend for programming in WinCE?? thanx...

  • My PDA's CPU is ARM,the demo project not work.why?

    Posted by Legacy on 08/07/2002 07:00am

    Originally posted by: ciml

    My PDA's CPU is ARM,the demo project not work.why?

  • It is very nice!, Except for MFC classes.

    Posted by Legacy on 08/14/2001 07:00am

    Originally posted by: sung-joo byun

    Nice! It works well.
    But, It doesn't work for MFC classes.

    Because CObject class already defined 'operator new',
    So, the other 'operator new' member is hidden.

    I solve this problem follow..

    Intesad of
    #define new new(_T(__FILE__), __LINE__)

    I added scope oprator :: for specifing global scope.
    #define new ::new(_T(__FILE__), __LINE__)

    It works well...

    p.s :

    have a nice day....

  • Only to HPC2000 and POCKET PC

    Posted by Legacy on 08/02/2001 07:00am

    Originally posted by: Dario Alves Junior

    How to do this component work with HPCPRO 2.11??

  • You must have javascript enabled in order to post comments.

Leave a Comment
  • Your email address will not be published. All fields are required.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date