| commit | a83d8f30d02f56e09f528a607d19b8665488821b | [log] [tgz] |
|---|---|---|
| author | Derek Bruening <bruening@google.com> | Tue Aug 29 05:53:46 2017 |
| committer | GitHub <noreply@github.com> | Tue Aug 29 05:53:46 2017 |
| tree | e4dd3f4bedd046613b8a09d9ed70785331f9d985 | |
| parent | eb6f0804ea9c09421a3f749b0f3a40258e466ada [diff] |
i#111 x64: enable 64-bit uninit read checking as default for Linux (#2036) Changes 64-bit Linux to no longer have pattern mode be the default: instead shadow-based full mode with uninitialized read checking is the default. Windows is not quite ready for this yet. Even on Linux we still have some major things like push, pop, and all esp adjusts still on the slowpath. Enables tests that were previously disabled for 64-bit. Disables several tests that fail on Travis but pass locally: i#111 covers further investigation. Issue: 111
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.
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. We also maintain a copy for online browsing.
The Dr. Memory package includes an “strace for Windows” tool called drstrace.
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/