-
Notifications
You must be signed in to change notification settings - Fork 104
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
Doesn't seem to support the VC140 compiler #28
Comments
Can you build and upload a test program? |
To get function names resolved:
|
As there has been no reply for 10 months, I'm closing this issue. Please post a message if you think this should be reopened. |
I haven't been able to reproduce this issue either way. |
hi @CyberShadow , I guess vs2015 has a link optimize, see https://blogs.msdn.microsoft.com/vcblog/2015/10/16/debugfastlink-for-vs2015-update-1/ In VS2017, I found I have to set Linker->Debugging->Generate Debug Info to "Generate Debug Information optimized for sharing and publishing (/DEBUG:FULL)", else I can't read all symbol names in PDB files with DIASDK(https://docs.microsoft.com/en-us/visualstudio/debugger/debug-interface-access/debug-interface-access-sdk). |
I've tried compiling with Could you provide instructions on how to compile a program with symbols that Very Sleepy can't read? Preferably from the command line (see e.g. https://github.com/VerySleepy/tests/blob/master/tests/msvc14/build.bat). |
please try: |
Thanks, that works. |
Should be fixed, can you try the latest build? |
When I click the process that previously was not working, sleepy stop responding.
|
Are you trying to attach to an existing process? What about launching a new process from Sleepy, does that work? How can I reproduce this? |
Could you download this: http://pan.baidu.com/s/1qYJaxcg |
Lauching a.exe in sleepy, and click "Stop", it show "Waiting for symbol query to start...". And cancel button is not working. |
Link doesn't seem to work. I think that if you put it in a .zip file, you can just attach it here, on GitHub. |
Everything works fine here... :/ Windows 10 x64 |
Sorry it doesn't work for me. Windows 10 x64 too. |
There might be a problem with your symbol settings. Check your symbol paths and try disabling using the symbol server. |
BTW, if it actually gets stuck in that function (and it's not just Very Sleepy calling that function in a loop), then the problem is in Microsoft's dbghelp.dll... |
I already tried disable the use symbol server in options |
Can you check whether the infinite loop occurs in Very Sleepy code, or in dbghelp code? You can do this by building Very Sleepy from source code, then placing a breakpoint on the |
Yes, I am sure it's in dbghelp code.
|
Thanks. Do you know if it only happens with the version of |
I use Process Explorer to view a.exe's thread callstack, it stop responding too. |
I had tried many dbghelp.dll, 32bit/64bit, in |
I tried adding
in |
Strange... I am out of ideas. I guess this is a MS DbgHelp bug. I don't know if it would help since it doesn't seem to depend on any other components, but maybe you could try installing the latest Windows SDK. The version this DbgHelp is from is 10.0.14393.0.
Yes: |
Hi, |
Could you please see if this issue occurs with the latest release: As the latest release includes many fixes, it's likely that this particular problem was fixed as well. If you encounter further problems, please leave a comment or open a new issue. Thanks! |
The function names are not resolved...
The text was updated successfully, but these errors were encountered: