-
Notifications
You must be signed in to change notification settings - Fork 646
Debug adapter process has terminated unexpectedly #564
Comments
I have the same problem, is there any workaround? Or how can I downgrade to the previous version of the extension? |
This commit looks suspicious 4938825 |
same problem. |
Same thing for me on OS X. |
Same for me on macOS Sierra version 10.12.1 As far as workarounds, there aren't any, but you can still run the app normally (without the debugger):
The recent macOS update seems to have created some issues for delve which might be related to this issue. See: https://github.com/derekparker/delve/issues |
The problem is this commit, which pulls in 'window' from the 'vscode' module - c35b419, which isn't available from the debug adapter. The import was there before, but since it was only pulling in types, typescript didn't output the We need a total separation between code that runs in the debug adapter, and code that runs in the extension host (or very careful sharing). |
No, I take that back sorry - the problem was 4938825 which pulls in util.ts, which shouldn't be in the debug adapter. I'll make a PR. |
Uhh... I can fix the crash but I'm just getting |
does delve work from the command line? That error looks like https://github.com/derekparker/delve/issues/645 |
No |
@sinhpham @soechin @jeremywho A new update is out (0.6.47) with the fix. Can you confirm that the issue is fixed for you? The Mac Sierra 10.12.1 still has problems with delve itself which is tracked in https://github.com/derekparker/delve/issues/645 |
0.6.47 fixed, thank you. |
Yep the latest version fixed it for me. Thanks. |
Great, happy coding! |
Smoke testing, Windows
Not sure if I'm doing something wrong, but I can't seem to get the debugger to launch on a basic hello world app.
The text was updated successfully, but these errors were encountered: