Memory leak finder

http://www.codeproject.com/KB/debug/Memory_leak_finder.aspx?msg=2823672#xx2823672xx
Download source files - 10.51 KBDownload DLL files - 19.08 KB

Introduction
Have you ever had a memory leak? Wished you knew where you allocated it and how? Is your boss cheap and refuses to buy Boundchecker or another debugging tool?
Here is the solution for you. A memory leak detector compiled directly into your code. It reports memory leaks with call stack of the allocation down to a user defined depth.
As an add-on, it does simple checks of the memory before and after the memory block, to track buffer overwrites.
Usage
Include tracealloc.cpp in your project. Define DETECT_LEAKS in the project settings. Compile. Run your application. Memory leaks are reported into your debug output window when the application terminates. Just click the memory leak and the correct file and line will be shown.
You can find further instructions in the source code.
How is it done?
The code overrides operator new and operator delete. For each allocation made, the code allocates extra space for tracking, call stack and no-mans-land. The current call stack is fetched and remembered, finally the code puts the newly allocated block in a linked list and the requested memory is returned.
When a memory block is deleted, the header is found and checked for buffer overwrites. The memory block is then removed from the linked list and deallocated.
When the program terminates, the global memory tracker object is deleted. The destructor traverses the linked list for memory blocks that isn’t deleted (= leaked memory). It then fetches symbol information for the call stacks and dumps the information in the debug console.
Limitations
The code is Microsoft Visual Studio and Win32 specific. It requires a debug build. The code is C++ specific. It handles new/delete but not malloc/free. The code will run slower with leak detection active (roughly at half normal debug build speed).
Finally
I want to thank Zoltan Csizmadia who wrote ExtendedTrace. I have used parts of his code for stack walking and symbol lookups.
I also want to thank the Code Project community. I have found many solutions or pointers in the right direction here. I hope I have given something back with this contribution.
Thank you!
License
This article, along with any associated source code and files, is licensed underThe MIT License
About the Author
Erik Rydgren

B.Sc in Software engineering
Writing software for the finance market.
Languages known: C/C++, SQL, Java, Perl, M68000 assembly and more. Give me the syntax and I'll program in it.
In my spare time i like to watch movies, read books and play computergames.
Occupation: Software Developer (Senior)
Location:Sweden
Other popular Debug Tips articles:
An introduction to debugging in MSVC++ using Pseudoregisters Explanation of the debugger pseudoregisters like @ERR, @TIB
Surviving the Release Version Learn about the issues and differences between Debug and Release builds.
Finding crash information using the MAP file Finding crash information using the MAP file: how to create and read the file
Post-Mortem Debugging Your Application with Minidumps and Visual Studio .NET This article describes how minidumps work, how to make your application create them when it crashes, and how to read them back with Visual Studio .NET.
Debugging Release Mode Problems A classic article on how to debug your release build applications