Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dr.memory run failed. #2502

Open
yuansunliang1988 opened this issue Jun 28, 2024 · 3 comments
Open

dr.memory run failed. #2502

yuansunliang1988 opened this issue Jun 28, 2024 · 3 comments

Comments

@yuansunliang1988
Copy link

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
Copy link

zhodzky commented Aug 8, 2024

Same problem. Has anyone found a solution?

@JosephCallahan
Copy link

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

@derekbruening
Copy link
Contributor

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., 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants