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 built on the DynamoRIO dynamic instrumentation tool platform.
Download Dr. Memory
Dr. Memory Performance
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 is included in the release package. A copy is available here for online browsing.
System Call Tracer for Windows
The Dr. Memory release includes drstrace, a system call tracer for Windows.
Fuzz Testing Infrastructure
Dr. Memory includes Dr. Fuzz, a fuzz testing mode along with a configurable fuzz testing library. Dr. Fuzz targets in-process function-level fuzzing, repeatedly running a target function while varying the inputs. It requires no access to source code, and supports code coverage-guided fuzzing, an input corpus, input dictionaries, and custom mutators.
Dr. Memory has its own discussion list.
Dr. Memory has its own Issue Tracker.
Contributing to Dr. Memory
We welcome contributions to Dr. Memory. We have a list of project ideas for contributors, targeted toward potential Google Summer of Code students as well as anyone else who is interested. Contributors must first sign a Contributor License Agreement.