This article needs additional citations for verification. (December 2011) (Learn how and when to remove this template message)
A memory debugger also known as a runtime debugger is a debugger for finding software memory problems such as memory leaks and buffer overflows. These are due to bugs related to the allocation and deallocation of dynamic memory. Programs written in languages that have garbage collection, such as managed code, might also need memory debuggers, e.g. for memory leaks due to "living" references in collections.
Memory debuggers work by monitoring memory access, allocations, and deallocation of memory. Many memory debuggers require applications to be recompiled with special dynamic memory allocation libraries, whose APIs are mostly compatible with conventional dynamic memory allocation libraries, or else use dynamic linking. Electric Fence is such a debugger which debugs memory allocation with malloc. Some memory debuggers (e.g. Valgrind) work by running the executable in a virtual machine-like environment, monitoring memory access, allocation and deallocation so that no recompilation with special memory allocation libraries is required.
Finding memory issues such as leaks can be extremely time consuming as they may not manifest themselves except under certain conditions. Using a tool to detect memory misuse makes the process much faster and easier.
As abnormally high memory utilization can be a contributing factor in software aging, memory debuggers can help programmers to avoid software anomalies that would exhaust the computer system memory, thus ensuring high reliability of the software even for long runtimes.
Comparison to static analyzerEdit
Some static analysis tools can also help find memory errors. Memory debuggers operate as part of an application while it's running while static code analysis is performed by analyzing the code without executing it. These different techniques will typically find different instances of problems, and using them both together yields the best result.
List of memory debugging toolsEdit
|AddressSanitizer||Linux, Mac OS||Free/open source (LLVM)||C, C++.||Compile-time instrumentation (available in Clang and GCC) and specialized library|
|Allinea DDT||Linux, Blue Gene||Proprietary commercial||C, C++ and F90. Also for parallel programs on supercomputers||Runtime - through dynamic linking|
|AQtime||Windows (Visual Studio, Embarcadero IDEs)||Proprietary commercial||.NET, C++, Java, Silverlight, JScript, VBScript||Runtime|
|BoundsChecker||Windows (Visual Studio)||Proprietary commercial||C++||Runtime intercepts or compile-time|
|Daikon||Unix, Windows, Mac OS X||Free/open source||Java, C/C++, Perl, and Eiffel||Runtime dynamic invariant detection|
|Debug_new||(general technique)||(general technique)||C++||Compile-time override|
|Deleaker||Windows||Proprietary commercial||C++, .Net||Runtime intercepts|
|dmalloc||Any||Free/open source||C||Compile-time override|
|DynamoRIO § Dr. Memory||Android, Linux, Windows||Free/open source (LGPL and BSD)||Any||Runtime intercepts|
|Electric Fence||Unix||Free/open source (GPL)||C, C++||Compile-time override|
|FASTMM4||Windows||Free/open source (GPL)||Delphi||Compile-time override|
|IBM Rational Purify||Unix, Windows||Proprietary commercial||C++, Java, .NET||Runtime|
|Insure++||Windows (Visual Studio plugin), Unix||Proprietary commercial||C, C++||source code instrumentation|
|Intel Inspector||Windows (Visual Studio)||Proprietary commercial||C, C++|
|libcwd||Linux (gcc)||Free/open source||C, C++||Compile-time override|
|libumem||Solaris||Bundled with Solaris||Link-time override|
|Memwatch||Any (programming library)||Free/open source||C||Compile-time override|
|mtrace||Various||Free/open source (LGPL)||GNU C library||Built-in, outputs accesses|
|MTuner||Various||Free||C, C++||Runtime intercepts, Link-time override (MSVC, Clang and GCC), Leak detection|
|Oracle Solaris Studio (formerly Sun Studio Runtime Checking)||Linux, Solaris||Proprietary freeware||C, C++, Fortran|
|OLIVER (APT international)||MVS, MVS/EXA, DOS/VSE||Proprietary software||IBM Assembler||Runtime intercepts, Hypervisor - Type 2|
|TotalView||Unix, Mac OS X||Proprietary commercial||C, C++, Fortran||Runtime|
|Valgrind § Memcheck||Linux, Mac OS, Android||Free/open source (GPL)||Any||Runtime intercepts|
|WinDbg||Windows||Proprietary freeware||C, C++, .NET, Python||Runtime|
- Michael C. Daconta: C++ Pointers and Dynamic Memory Management, John Wiley & Sons, ISBN 0-471-04998-0
- Andrew Koenig: C Traps and Pitfalls, Addison-Wesley, ISBN 0-201-17928-8
- Globus, A; Raible, E (July 1994). "Fourteen ways to say nothing with scientific visualization". IEEE Computer. 27 (7): 86–88. doi:10.1109/2.299418. Retrieved August 24, 2017.
- "Review: 5 memory debuggers for Linux coding". Retrieved August 24, 2017.
- "Dynamic Analysis vs. Static Analysis". Retrieved August 24, 2017.