Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Debug adapter process has terminated unexpectedly #564

Closed
mousetraps opened this issue Oct 26, 2016 · 14 comments
Closed

Debug adapter process has terminated unexpectedly #564

mousetraps opened this issue Oct 26, 2016 · 14 comments

Comments

@mousetraps
Copy link

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.
image

@sinhpham
Copy link

I have the same problem, is there any workaround? Or how can I downgrade to the previous version of the extension?

@sinhpham
Copy link

This commit looks suspicious 4938825

@soechin
Copy link

soechin commented Oct 27, 2016

same problem.

@jeremywho
Copy link

Same thing for me on OS X.

@ashneverdawn
Copy link

ashneverdawn commented Oct 27, 2016

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):

  1. Open Integrated terminal (ctrl+`)
  2. Run the following command:

go run yourFileName.go

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

@roblourens
Copy link
Member

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 require.

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).

@roblourens
Copy link
Member

roblourens commented Oct 27, 2016

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.

@roblourens
Copy link
Member

roblourens commented Oct 27, 2016

Uhh... I can fix the crash but I'm just getting could not launch process: could not get thread count from delve right now. It worked earlier, on sierra, and the same go/delve versions.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Oct 27, 2016

does delve work from the command line?

That error looks like https://github.com/derekparker/delve/issues/645
@roblourens are you trying on Mac or Windows?

@roblourens
Copy link
Member

No

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Oct 27, 2016

@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

@soechin
Copy link

soechin commented Oct 27, 2016

0.6.47 fixed, thank you.

@sinhpham
Copy link

Yep the latest version fixed it for me. Thanks.

@ramya-rao-a
Copy link
Contributor

Great, happy coding!

@ramya-rao-a ramya-rao-a added the bug label Nov 1, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants