i#2498 init failures: Ignore privlib init failures (#2515)

Updates DR to 51b152fa2 extends the private loader bcrypt.dll entry
failure being ignored to ignore all private library entry failures. We
have had multiple cases of initializers failing without fatal
consequences, and given that we do not have resources to track down
every detail it is best to note the failure and move on. We have seen
Dr. Memory in particular fail on newer Windows versions and in some
cases ignoring that failure lets the tool continue and succeed, as only
a small piece of the private library is needed (generally pulled in as a
chain of dependences from dbghelp.dll which is used for symbol
information). The private loader on Windows is considered best-effort at
this point.

Issue: #2498
1 file changed
tree: 528390a31336cb8a307fed24d4f1cd7b8a1e1d31
  1. .github/
  2. common/
  3. docs/
  4. drfuzz/
  5. drheapstat/
  6. drltrace/
  7. drmemory/
  8. drstrace/
  9. drsymcache/
  10. drsyscall/
  11. framework/
  12. make/
  13. tests/
  14. third_party/
  15. tools/
  16. umbra/
  17. wininc/
  18. .gitmodules
  19. ACKNOWLEDGEMENTS
  20. CMakeLists.txt
  21. codereview.cmake
  22. CONTRIBUTING.md
  23. CTestConfig.cmake
  24. lgpl-2.1.txt
  25. license.txt
  26. package.cmake
  27. README
  28. README.md
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.

Dr. Memory 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/