-
Notifications
You must be signed in to change notification settings - Fork 1
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
Debugger Hangs #5
Comments
I came to submit this issue. I experienced the problem across-the-board running Windows and using dashmips in both wsl and powershell from vscode 1.47.3 and dashmips 0.1.6 and 0.1.5 installed via pip. I was thinking there may be an issue relating to calling the interpreter on windows, or having multiple possible shells, so I tried it also on ubuntu the same vscode and dashmips installations. I'm new to dashmips, so I'm not sure here, but the problem seems to extend beyond vscode? If I run As an aside, EDIT: |
Thanks for noticing this, I've fixed the |
Thanks for helping out our project! |
This has been resolved! |
[Interpreter]
When you go to debug a mips file the debugger never gets the go ahead to start debugging from the interpreter. I suspect this has to do with the issues surrounding the code in
https://github.com/nbbeeken/dashmips/blob/master/dashmips/debuggerserver.py
With the
asyncio
python code, it is the same place where the interpreter fails to exit correctly since the event loop never gets shutdown. I went with the async code cus its cool, if you find it might be easier to just switch to the synchronous api go for it, async in python isn't as friendly as it is in Javascript.[Debugger]
It could be that there's some more convenient APIs in the newer vscode debugger extension code. I'd take a look at their docs on what kinda actions they provide. I think its unlikely that it's vscode's fault but certainly
RunInTerminal Request
is something to exploreThe text was updated successfully, but these errors were encountered: