Memory monitoring tool capable of identifying memory-related programming errors.
Dr. Memory is a memory monitoring tool designed to identify memory-related programming errors in applications running on Windows, Linux, Mac, and Android. It helps developers detect issues such as accesses to uninitialized or unaddressable memory, use-after-free, double frees, memory leaks, handle leaks (Windows), GDI API usage errors, and accesses to unreserved thread local storage slots.
Key Features:
Detection of uninitialized memory access
Identification of heap overflow/underflow and use-after-free issues
Monitoring for memory and handle leaks
Analysis of GDI-related errors on Windows
Thread local storage slot validation
Cross-platform support for IA-32, AMD64, and ARM architectures
Audience & Benefit:
Ideal for software developers and testers seeking reliable memory analysis without modifying application binaries. Dr. Memory helps improve code quality by identifying hard-to-spot memory bugs early in the development cycle, reducing debug time, and enhancing application performance and reliability across multiple operating systems.
Dr. Memory can be installed via winget, making it accessible for integration into various development environments.
README
Dr. Memory: the memory debugger
About Dr. Memory
Dr. Memory is a memory monitoring tool capable of identifying
memory-related programming errors such as accesses of uninitialized memory,
accesses to unaddressable memory (including outside of allocated heap units
and heap underflow and overflow), accesses to freed memory, double frees,
memory leaks, and (on Windows) handle leaks, GDI API usage errors, and
accesses to un-reserved thread local storage slots.
Dr. Memory operates on unmodified application binaries running on Windows,
Linux, Mac, or Android on commodity IA-32, AMD64, and ARM hardware.
Dr. Memory is released under an LGPL license and binary packages are
available for download.
Dr. Memory is faster than comparable tools, including Valgrind, as shown in
our CGO 2011 paper Practical Memory Checking with
Dr. Memory,
where we compare the two tools on Linux on the SPECCPU 2006 benchmark
suite:
(Valgrind is unable to run 434.zeusmp and 447.dealII).
Documentation
Documentation is included in the release package. We also maintain a copy
for online browsing.
