-
Notifications
You must be signed in to change notification settings - Fork 262
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
Drmemory.exe unable yto load client library:bcrpt.dll: library initializer failed #2498
Comments
I think this was fixed by DynamoRIO/dynamorio#6571 |
Pulled into drmemory by #2495 |
derekbruening
added a commit
that referenced
this issue
Sep 23, 2024
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
derekbruening
added a commit
that referenced
this issue
Sep 23, 2024
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
derekbruening
added a commit
that referenced
this issue
Sep 24, 2024
Adds bcrypt.dll to the allowlist of known libraries we expect to potentially see inside the drmemory.exe process. Issue: #2498
derekbruening
added a commit
that referenced
this issue
Sep 24, 2024
Adds bcrypt.dll to the allowlist of known libraries we expect to potentially see inside the drmemory.exe process. Issue: #2498
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I try to use Drmemory.exe to analyse my exe to find problem, it shows the following error:
Unbale to load client library: bcrypt.dll: library initializer failed
But I can found the bcrypt.dll in n my system file
And my version info:
How could I fix these problem
The text was updated successfully, but these errors were encountered: