DynamoRIO / drmemory

Memory Debugger for Windows, Linux, Mac, and Android
Other
2.44k stars 262 forks source link

dr.memory run failed. #2502

Open yuansunliang1988 opened 4 months ago

yuansunliang1988 commented 4 months ago

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

zhodzky commented 2 months ago

Same problem. Has anyone found a solution?

JosephCallahan commented 2 weeks ago

Same for me. No A/V, Windows Defender disabled.

derekbruening commented 2 weeks ago

As the bug template (deleted by the filer here?) https://github.com/DynamoRIO/drmemory/issues/new?assignees=&labels=&template=bug_report.md&title= and https://drmemory.org/page_help.html#autotoc_md12 show there are several steps that can obtain more information if the tool fails to start up.

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., https://github.com/DynamoRIO/dynamorio/issues/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.