Memory debugger explained

A memory 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.

Overview

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.[1]

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 analyzer

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.[2]

List of memory debugging tools

This is a list of tools useful for memory debugging. A profiler can be used in conjunction with a memory debugger.

NameOSLicenseLanguagesTechnique
AddressSanitizerLinux, Mac OSFree/open source (LLVM)C, C++, RustCompile-time instrumentation (available in Clang and GCC) and specialized library
Allinea DDTLinux, Blue Gene commercialC, C++ and F90. Also for parallel programs on supercomputersRuntime - through dynamic linking
AQtimeWindows (Visual Studio, Embarcadero IDEs) commercial.NET, C++, Java, Silverlight, JScript, VBScript[3] Runtime
BcheckSolaris
BoundsCheckerWindows (Visual Studio) commercialC++Runtime intercepts or compile-time
DaikonUnix, Windows, Mac OS X[4] Free/open source[5] Java, C/C++, Perl, and EiffelRuntime dynamic invariant detection
Debug_new(general technique)(general technique)C++Compile-time override
DeleakerWindows (standalone, and plugins for Visual Studio, RAD Studio, Qt Creator, CLion) commercialC++, .Net, DelphiRuntime intercepts
dmallocFree/open sourceCCompile-time override
Android, Linux, WindowsFree/open source (LGPL and BSD)Runtime intercepts
Electric FenceUnixC, C++Compile-time override
FASTMM4WindowsDelphiCompile-time override
IBM Rational PurifyUnix, Windows commercialC++, Java, .NETRuntime
Insure++Windows (Visual Studio plugin), Unix commercialC, C++source code instrumentation
Intel InspectorWindows (Visual Studio), Linux commercialC, C++, FortranRuntime
libcwdLinux (gcc)Free/open sourceC, C++Compile-time override
libumemSolarisBundled with SolarisLink-time override
Memwatch (programming library)Free/open sourceCCompile-time override
mtraceGNU C libraryBuilt-in, outputs accesses
MTunerC, C++Runtime intercepts, Link-time override (MSVC, Clang and GCC), Leak detection
Oracle Solaris Studio (formerly Sun Studio Runtime Checking)Linux, SolarisProprietary freewareC, C++, Fortran
OLIVER (APT international)MVS, MVS/EXA, DOS/VSE softwareIBM AssemblerRuntime intercepts, Hypervisor - Type 2
TotalViewUnix, Mac OS X commercialC, C++, FortranRuntime
Linux, Mac OS, AndroidRuntime intercepts
WinDbgWindows freewareC, C++, .NET, PythonRuntime

See also

References

C Traps and Pitfalls, Addison-Wesley,

External links

Notes and References

  1. Web site: Review: 5 memory debuggers for Linux coding. August 24, 2017. 20 November 2015.
  2. Web site: Dynamic Analysis vs. Static Analysis. August 24, 2017.
  3. Web site: Managed Code - AQtime Pro | SmartBear . 2013-01-14 . https://web.archive.org/web/20130919153515/http://smartbear.com/products/qa-tools/application-performance-profiling/profiling-managed-code . 2013-09-19 . dead .
  4. Web site: The Daikon Invariant Detector User Manual.
  5. Web site: The Daikon Invariant Detector User Manual.