Click here to Skip to main content
Click here to Skip to main content

Memory Leak detection Program without using any tools

, 8 Apr 2008 CPOL
Rate this:
Please Sign up or sign in to vote.
Without using any tools, This program will find the memory leak in your program

Introduction

In market, there are a lot of tools for detecting the memory leaks. Here I made a program which has to include in your source file and it will tell the desired informations to find where memory leaks happen.

There are two files one is findLeak.c and other is findLeak.h . Source file is test.c , this is your program which you want to check memory leaks.

Concept is that when user call library function "malloc or calloc " for allocating dynamic memory, then we have to call our malloc or calloc (In case of my source code 'MyCalloc' function in place of 'calloc' and MyMalloc function in place of 'malloc'). So we have to define malloc to your malloc and in .c file you have to undef malloc and calloc By this way we can call our MyMalloc or MyCalloc function and in this function we will call another function which keeps all info about how much memory allocated. We will do the same for Library function "free" to deallocating memory( In my source file "MyFree" is used in plae of free function).

Using the code


Now for keeping information, i made a simple singly linked list. which will add info about memory when user call "malloc" or "calloc" function and will also keep information when user call "free" function.

By program you can easily understand.

Heder File : findLeak.h

#define   uint          unsigned int 
#define   cchar         const char  
#define  OutFile       "/home/asadulla/test/MemLeakInfo.txt"   // Just Suppose

#define  MAX_FILENAME_LENGTH    256
#define  calloc(objs, nSize)    MyCalloc (objs, nSize, __FILE__, __LINE__)
#define  malloc(nSize)          MyMalloc (nSize, __FILE__, __LINE__)
#define  free(rMem)             MyFree(rMem)

// This structure is keeping info about memory leak

struct InfoMem
{
    void *addr;
    uint nSize;
    char fileName[MAX_FILENAME_LENGTH];
    uint lineNumber;
};

typedef struct InfoMem infoMem;

//This is link list of InfoMem which keeps a List of memory Leak in a source file

struct LeakMem
{
    infoMem memData;
    struct LeakMem *nxt;
};

typedef struct LeakMem leakMem;

void WriteMemLeak(void);

void SubAddMemInfo(void *rMem, uint nSize,  cchar  *file, uint lno);

void SubAdd(infoMem alloc_info);

void ResetInfo(uint pos); //erase

void DeleteAll(void); //clear(void);

void *MyMalloc(uint size, cchar *file, uint line);

void *MyCalloc(uint elements, uint size, cchar * file, uint lno);

void  MyFree(void * mem_ref);



Source File : findLeak.c

#include    <span class="code-keyword"><stdio.h></span>
#include    <span class="code-keyword"><malloc.h></span>
#include    <span class="code-keyword"><string.h></span>
#include    <span class="code-string">"findLeak.h"</span>

#undef        malloc
#undef        calloc
#undef         free

static leakMem * ptr_start = NULL;
static leakMem * ptr_next =  NULL;

// -----------------------------------------------------------

// Name: MyMalloc

// Desc: This is hidden to user. when user call malloc function then 
//       this function will be called.

void *MyMalloc (uint nSize, cchar* file, uint lineNumber)
{
    void * ptr = malloc (nSize);
    if (ptr != NULL) 
    {
        SubAddMemInfo(ptr, nSize, file, lineNumber);
    }
    return ptr;
}


// -----------------------------------------------------------

// Name: MyCalloc

// Desc: This is hidden to user. when user call calloc function then 
//       this function will be called.

void * MyCalloc (uint elements, uint nSize, const char * file, uint lineNumber)
{
    uint tSize;
    void * ptr = calloc(elements , nSize);
    if(ptr != NULL)
    {
        tSize = elements * nSize;
        SubAddMemInfo (ptr, tSize, file, lineNumber);
    }
    return ptr;
}



// -----------------------------------------------------------

// Name: SubAdd

// Desc: It's actually  Adding the Info.


void SubAdd(infoMem alloc_info)
{
    leakMem * mem_leak_info = NULL;
    mem_leak_info = (leakMem *) malloc (sizeof(leakMem));
    mem_leak_info->

These two files (header file and source file) user has to include in his source file to which user want to find memory leak.

Source File for detecting memory leak is as Here you can gice your own source file and in this source file you have write onle line to include file #include"findLeak.h"


Testing : test.c

Code: c
#include<span class="code-keyword"><malloc.h></span>
#include<span class="code-string">"findLeak.h"</span>

int main()
{
     int *p1 = (int *)malloc(10);
     int *p2 = (int *)calloc(10, sizeof(int));
     char *p3 = (char *) calloc(15, sizeof(float));
     float *p4 = (float*) malloc(16);
     free(p2);
     WriteMemLeak();
     return 0;
 }

Now user can compile these programmes in a console as :
> g++ test.c findLeak.c
and give a command for run
> ./a.out

then go to you your directory where you have defined a macro "OutFile" and open this defined file and you can see the results.

Output of above source file is as:

Code: output
SUMMARY ABOUT MEMORY LEAKS OF YOUR SOURCE FILE 
     -----------------------------------

Name of your Source File                 : test.c
Starting Address                         : 184960
Total size Of memory Leak                : 10 bytes
Line Number for which no DeAllocation    : 7
-----------------------------------
-----------------------------------

Name of your Source File                 : test.c
Starting Address                         : 187104
 Total size Of memory Leak               : 60 bytes
Line Number for which no DeAllocation    : 9

-----------------------------------
-----------------------------------
Name of your Source File                 : test.c
Starting Address                         : 184984
 Total size Of memory Leak               : 16 bytes
Line Number for which no DeAllocation    : 10
-----------------------------------
----------------------------------- 



Now you can try to make you own Test Cases just like test.c.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

asadullah ansari
Software Developer (Senior) Huawei Technologies
India India
Me Not Small Not Big Also but I Can be Broken Easily. That's I...

Comments and Discussions

 
GeneralMy vote of 5 PinmemberMember 963329426-Nov-12 16:24 
GeneralReally good article Pinmemberjack2k8529-Sep-09 4:06 
GeneralMy vote of 1 PinmemberFrank Heimes13-Jan-09 23:25 
GeneralVery good article. Though there is a flaw in it. PinmemberVipin Kr. Sharma14-Aug-08 1:27 
GeneralGood start Pinmemberaxelriet9-Apr-08 2:08 
GeneralRe: Good start Pinmemberasadullah ansari9-Apr-08 2:51 
good suggestion!!! I will do. This is my first article. I am new to this forum.
GeneralRe: Good start Pinmemberalramesh9-Apr-08 21:14 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web03 | 2.8.141015.1 | Last Updated 9 Apr 2008
Article Copyright 2008 by asadullah ansari
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid