| commit | 82fb3466a8398532e54b5d2615828ff987982f3f | [log] [tgz] |
|---|---|---|
| author | diversenok <[email protected]> | Tue Jul 01 02:37:49 2025 |
| committer | GitHub <[email protected]> | Tue Jul 01 02:37:49 2025 |
| tree | ff4d7dc9c8c2cecb7d53e44546c467ee99043292 | |
| parent | fbc75a3abf39ebbe66c489772ed7295fcaaca120 [diff] |
Fix NtUserOpenClipboard (#2558) This pull request updates the definition for `NtUserOpenClipboard` to reflect that the syscall writes to a pointer provided in the second argument. `OpenClipboard` passes an address of a local variable to this parameter and then reads from it, causing the following warning: ``` Error #1: UNINITIALIZED READ: reading 0x00000092296ff998-0x00000092296ff99c 4 byte(s) # 0 USER32.dll!OpenClipboard # 1 main Note: @0:00:00.082 in thread 11352 Note: instruction: cmp 0x38(%rsp) $0x00000000 ```
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/