commit | d56d49eda5e84d78a55d17be7b5cf40e991b75cd | [log] [tgz] |
---|---|---|
author | Derek Bruening <bruening@google.com> | Sun Mar 17 21:47:16 2019 |
committer | GitHub <noreply@github.com> | Sun Mar 17 21:47:16 2019 |
tree | 06a9cd13a0805dea3ed90d561fcfc3c943f3a2b0 | |
parent | 93fa04463985f7b6ba49abeb6b487448c72b5c70 [diff] |
i#111 x64: Fix or suppress failing win64 tests (#2179) Fixes tests/operators taking forever on its OOM test by tweaking the code to avoid compiler warnings on very large allocations. Fixes x64 bugs in handle stack operations: + Handle DR rip-rel mangling when decoding from the cache on the esp adjust slowpath. + Add an x64 chkstk pattern match. Expands the i#2170 suppression to match ntdll.dll!RcConsolidateFrames. Suppress the rest of the win64 full mode failing tests to get Appveyor green. Issue: #111, #2170, #2180
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/