-
Notifications
You must be signed in to change notification settings - Fork 255
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
Unable to load DLL 'dbgeng.dll': The specified procedure could not be found. (Exception from HRESULT: 0x8007007F) #78
Comments
I just had the same issue. I added a possible workaround to the original issue. |
@cklutz Thanks for the comment. Now I got the error on "mrt100dac_winamd64.dll". Any idea? Update: |
I'm not quite sure what to do with this one. I may end up adding a more descriptive error message when it happens. I specifically don't specify where to load dbgeng.dll to let the application developer choose which one to load specifically (as with the workaround cklutz posted). I do this very often myself using a more up to date version than what's shipped in system32. |
Hello! This issue is being closed due to its age. The codebase has moved significantly since this was filed. Please feel free to open a new issue for ClrMD about this issue if it still reproduces on ClrMD 1.0. (Also, I apologize for having not looked at or resolved this earlier and for resolving it now. In order for me to be able to make some progress on the growing issue count in ClrMD I need to clear the backlog down to a manageable set of issues, but do feel free to file a new one if this is still a problem.) Please @leculver if you reply to this message to make sure I get it. |
Note: There is already an issue similar to this but it's pretty old and its closed.
ClrMD version: 0.8.31.0
.NET Framework: 4.5.1
Architecture: 86 and 64
OS: Windows 10
dbgeng.dll exist in c:\windows\system32 (also dbgcore and dbghelp if it matter)
When I call
DataTarget.AttachToProcess(id, milliseconds, AttachFlag.NonInvasive)
I got this error every time.Stack trace:
The text was updated successfully, but these errors were encountered: