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

Entry Point Not Found #7

Closed
gpakosz opened this issue Feb 17, 2014 · 7 comments
Closed

Entry Point Not Found #7

gpakosz opened this issue Feb 17, 2014 · 7 comments

Comments

@gpakosz
Copy link

gpakosz commented Feb 17, 2014

Just tried to launch Very Sleepy CS on Windows 8.1 64bit.

I'm getting an error dialog saying:

The procedure entry point SetCheckUserInterruptShared could not be located in the dynamic link library C:\WINDOWS\SYSTEM32\dbgeng.dll

Oddly enough, verysleepy_0_82.exe from which you forked works.

@CyberShadow
Copy link
Member

That would be caused by the dbgeng dependency, which we need for late symbol lookup.

Can you check where exactly the problem is with Dependency Walker?

@gpakosz
Copy link
Author

gpakosz commented Feb 17, 2014

Looks like so, I emailed you the Dependency Walker output file.

@CyberShadow
Copy link
Member

Thanks! That makes the problem obvious: we load the system dbgeng, which then tries to load dbghelp, but instead of loading the system one, it's loading Sleepy's version, which is too old for the system dbgeng.

So the fix would be to update the dbghelp included with Sleepy. A workaround that would probably work would be to just delete Sleepy's dbghelp.dll.

@gpakosz
Copy link
Author

gpakosz commented Feb 17, 2014

Removing Sleepy's dbghelp.dll works around the problem indeed. Should I also remove dbghelpw.dll and dbghelpw_wow64.dll?

@CyberShadow
Copy link
Member

Nope, that won't be necessary, as those have nonstandard names and thus can't conflict with system DLLs.

@gpakosz
Copy link
Author

gpakosz commented Feb 17, 2014

Alright. Thank you for the quick feedback. Appreciated.

@CyberShadow
Copy link
Member

It looks like I had already fixed this problem in the then-upcoming v0.90 (by renaming our dbghelp.dll to dbghelpms.dll) by the time this issue was opened (commit c4b9a50). I must have forgotten that I fixed it. I'm guessing you were using v0.83, which still had the problem.

Please try the latest version, and feel free to reopen if this problem occurs again.

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

No branches or pull requests

2 participants