Memory Debugger for Windows, Linux, Mac, and Android
C C++ CMake Perl Objective-C Shell Other
Latest commit bcb3607 Jul 6, 2017 @mxmssh mxmssh committed on GitHub i#2006: fixes drltrace test failures on Android (#2008)
Added copying of config file on Android device.

Fixes #2006
Permalink
Failed to load latest commit information.
common i#1990: C++11 requires space between literal and string macro (#1991) May 17, 2017
docs Fix Dr. Heapstat documentation build error Jan 25, 2016
drfuzz i#1923, DRi#2127, DRi#1374: eliminate UNIX symlink library versioning Jan 10, 2017
drheapstat Add uint64 type support to the options infrastructure Dec 16, 2015
drltrace i#2006: fixes drltrace test failures on Android (#2008) Jul 6, 2017
drmemory i#1969: use a long jne for inheap_slot instru (#1971) Mar 20, 2017
drstrace i#1349 build drltrace parallel to drstrace : frontend (#1943) Mar 2, 2017
drsymcache i#1923, DRi#2127, DRi#1374: eliminate UNIX symlink library versioning Jan 10, 2017
drsyscall i#1948 add libcall args sym printing: syscall args support (#1975) Apr 14, 2017
dynamorio @ 266b8a3 DRi#2453: add XP support for VS2013 builds (#1998) May 30, 2017
framework DRi#2224: avoid asking for size from dr_safe_* (#1950) Mar 13, 2017
make i#1952: fix build failures with SDK 8.1 and 64-bit cmake (#1953) Mar 14, 2017
tests i#1952: fix build failures with SDK 8.1 and 64-bit cmake (#1953) Mar 14, 2017
third_party i#573,i#1636 annotations: add leak check annotation handling Sep 23, 2015
tools i#1908 syscall files: adds auto-generation and testing Aug 27, 2016
umbra Umbra docs: Adds note to umbra_insert_app_to_shadow (#1999) Jun 4, 2017
wininc i#1885: false pos in TppIsWorkerThread May 2, 2016
.appveyor.yml DRi#2406 faster appveyor: drop VS2010 support (#1997) May 30, 2017
.gitmodules change submoudles url from dynamorio to dynamorio.git to make buildbo… Dec 1, 2014
.travis.yml i#1938: initial AppVeyor config (#1939) Feb 21, 2017
ACKNOWLEDGEMENTS Update ACKNOWLEDGEMENTS list of contributors Aug 9, 2014
CMakeLists.txt DRi#2167 shrink pdbs: set space-saving linker options (#1994) May 30, 2017
CONTRIBUTING.md Point at the new Latest-Build wiki page for per-commit builds Feb 14, 2016
CTestConfig.cmake Code cleanup: remove trailing spaces from the end of lines Jan 9, 2014
README i#1850 Android, i#1726 ARM: update README and docs for new platforms Feb 2, 2016
README.md i#1850 Android, i#1726 ARM: update README and docs for new platforms Feb 2, 2016
codereview.cmake Code cleanup: remove trailing spaces from the end of lines Jan 9, 2014
lgpl-2.1.txt initial sources for public repository Jun 7, 2010
license.txt i#1349 build drltrace parallel to drstrace: clean copy (#1941) Feb 22, 2017
package.cmake Fix Mac package build failure Oct 17, 2015

README.md

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

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: http://drmemory.org/