You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PS D:\Program Files (x86)\Dr. Memory\bin64> drmemory.exe -check_leaks -logdir "d:\log" E:\a.exe Dr.M WARNING: unable to locate results file: can't open d:\log/resfile.10080 (code=2).
Dr. Memory failed to start the target application, perhaps due to
interference from invasive security software.
Try disabling other software or running in a virtual machine.
WARNING: Examine the following unusual libraries in this process to help identify
invasive software that may have affected the target application:
C:\Windows\System32\bcrypt.dll
Please file a bug about this at http://drmemory.org/issues Dr.M WARNING: application exited with abnormal code 0xffffffff
The text was updated successfully, but these errors were encountered:
The best is to run plain DynamoRIO via drrun on a console application (not a graphical application). E.g.:
dynamorio\bin64\drrun -- msg
Debug build may provide more information:
dynamorio\bin64\drrun -debug -- msg
There are 2 known sources of problems: security software on the machine invasively installing hooks in every process (e.g., DynamoRIO/dynamorio#7024) and DynamoRIO's private loader having a problem with the system libraries (e.g., #2456) while trying to support Microsoft's dbghelp library inside the application process. Most likely you are hitting one or the other, which the above command should hep identify.
PS D:\Program Files (x86)\Dr. Memory\bin64> drmemory.exe -check_leaks -logdir "d:\log" E:\a.exe
Dr.MWARNING: unable to locate results file: can't open d:\log/resfile.10080 (code=2).Dr. Memory failed to start the target application, perhaps due to
interference from invasive security software.
Try disabling other software or running in a virtual machine.
WARNING: Examine the following unusual libraries in this process to help identify
invasive software that may have affected the target application:
Please file a bug about this at http://drmemory.org/issues
Dr.MWARNING: application exited with abnormal code 0xffffffffThe text was updated successfully, but these errors were encountered: