Dr. Memory
Obtaining Help and Reporting Bugs

For questions, bug reports, and discussion, join the Dr. Memory Users group.

The Dr. Memory issue tracker is located at: http://drmemory.org/issues

If a problem in the Dr. Memory tool itself is encountered, try the following steps to help diagnose the issue:

  • Run the debug version of Dr. Memory and of its underlying engine DynamoRIO by passing "-debug -dr_debug -pause_at_assert" to drmemory.exe. Are any messages reported?
  • Try running light mode ("-light"). Does the issue appear there?
  • Try running "-leaks_only -no_count_leaks -no_track_allocs". Does that work?
  • Try a recent build from http://build.chromium.org/p/client.drmemory/builds/
  • Try disabling anti-virus or other invasive software, as it may not interoperate well with Dr. Memory (see Interoperability).

To supply data for analyzing and fixing a bug, reproduce the problem using these options to Dr. Memory:

-dr_ops "-dumpcore_mask 0x8bff"

and provide the resulting <appname>.exe.<pid>.00000000.ldmp file from the <installpath>/drmemory/logs/dynamorio/ directory. The ldmp should compress nicely.

If there is no ldmp produced, try asking for an ldmp on application faults and not just tool faults:

-dr_ops "-dumpcore_mask 0x48bff"

Additionally, if the run is pretty short, run with the "-verbose 2" option and attach the resulting global.<pid>.log file from the same directory as the results.txt file (compress it if large).