Clone this repo:
  1. 2a75c91 i#1948 library calls arguments printing:gdi32 and advapi32 dlls (#2048) by Maksim Shudrak · 3 weeks ago master release_2.0.0_rc2
  2. afc1d71 i#111 win64, part 1: syscall and native call updates (#2055) by Derek Bruening · 3 weeks ago
  3. 68b0543 i#2041: use drutil_insert_get_mem_addr() (#2054) by Derek Bruening · 3 weeks ago
  4. 62cbd37 DRi#2641: fix failures on Travis (#2053) by Derek Bruening · 3 weeks ago
  5. 2b95a42 i#2039: Opts out of auto-predication (#2042) by Toshi Piazza · 8 weeks ago

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 built on the DynamoRIO dynamic instrumentation tool plaform.

DynamoRIO logo

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:

Performance chart

(Valgrind is unable to run 434.zeusmp and 447.dealII).


Documentation is included in the release package. We also maintain a copy for online browsing.

System call tracer for Windows

The Dr. Memory package includes an “strace for Windows” tool called drstrace.

Obtaining help

Dr. Memory has its own discussion list.

To report a bug, use the issue tracker.

See also the Dr. Memory home page: