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

Cannot debug after update #575

Closed
andiyudistira opened this issue Oct 27, 2016 · 8 comments
Closed

Cannot debug after update #575

andiyudistira opened this issue Oct 27, 2016 · 8 comments

Comments

@andiyudistira
Copy link

I got this error message while trying to debug my go app after update the plugin to version 0.6.46 - 26th October 2016:
Debug adapter process has terminated unexpectedly

I can debug without any issues before I update the plugin.

@i5on9i
Copy link

i5on9i commented Oct 27, 2016

Me, either. I've just installed Go plugin, but it doesn't work with the error message like the "andiyudistira " said

Go ver. : amd64 go 1.7.3
windows : windows 10 64bit
dlv version : 0.11.0-alpha

messageService.ts:128 Debug adapter process has terminated unexpectedly: Error: Debug adapter process has terminated unexpectedly
at Object.f [as create](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:29:18882)
at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:122:4977
at Object.v [as _notify](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:8549)
at Object.enter (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:12054)
at _run (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:13375)
at _chainedError (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:12734)
at n (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:10557)
at then (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:14184)
at Object.enter (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:10626)
at _run (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:13375)
at _setCompleteValue (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:31:13069)e.doShow @ messageService.ts:128e.show @ messageService.ts:107(anonymous function) @ actionRegistry.ts:156done @ winjs.base.raw.js:1378v @ winjs.base.raw.js:1224enter @ winjs.base.raw.js:901_run @ winjs.base.raw.js:1068_chainedError @ winjs.base.raw.js:1031n @ winjs.base.raw.js:736then @ winjs.base.raw.js:1436enter @ winjs.base.raw.js:747_run @ winjs.base.raw.js:1068_setCompleteValue @ winjs.base.raw.js:1052v @ winjs.base.raw.js:1209enter @ winjs.base.raw.js:901_run @ winjs.base.raw.js:1068_chainedError @ winjs.base.raw.js:1031n @ winjs.base.raw.js:736then @ winjs.base.raw.js:1436enter @ winjs.base.raw.js:747_run @ winjs.base.raw.js:1068_setCompleteValue @ winjs.base.raw.js:1052v @ winjs.base.raw.js:1209enter @ winjs.base.raw.js:901_run @ winjs.base.raw.js:1068_chainedError @ winjs.base.raw.js:1031n @ winjs.base.raw.js:736then @ winjs.base.raw.js:1436enter @ winjs.base.raw.js:747_run @ winjs.base.raw.js:1068_setCompleteValue @ winjs.base.raw.js:1052g @ winjs.base.raw.js:1170enter @ winjs.base.raw.js:852_run @ winjs.base.raw.js:1068_completed @ winjs.base.raw.js:1036then @ winjs.base.raw.js:1566enter @ winjs.base.raw.js:747_run @ winjs.base.raw.js:1068_setCompleteValue @ winjs.base.raw.js:1052v @ winjs.base.raw.js:1209enter @ winjs.base.raw.js:901_run @ winjs.base.raw.js:1068_error @ winjs.base.raw.js:1041(anonymous function) @ v8Protocol.ts:59_cancelAction @ winjs.base.raw.js:1652enter @ winjs.base.raw.js:805_run @ winjs.base.raw.js:1068cancel @ winjs.base.raw.js:964_cancelAction @ winjs.base.raw.js:1311enter @ winjs.base.raw.js:805_run @ winjs.base.raw.js:1068cancel @ winjs.base.raw.js:964(anonymous function) @ rawDebugSession.ts:292(anonymous function) @ rawDebugSession.ts:292

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Oct 27, 2016

Any errors in the console (Run Developer: Toggle Developer Tools and check the console) or in the Go channel in the output window?

In your launch.json, do you have a port configured?

The one change we did in the debug side of the extension is to choose a random port instead of the hard coded 2345 if no ports are configured in launch.json

cc @roblourens

@i5on9i
Copy link

i5on9i commented Oct 27, 2016

i've posted errors here again,
and, i didnt set the port.
i used the config like the below

{
            "name": "Launch",
            "type": "go",
            "request": "launch",
            "mode": "debug",
            "program": "${workspaceRoot}",
            "env": {},
            "args": []
},

11.png

@lukehoban
Copy link
Contributor

See also #564 which appears to be the same issue.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Oct 27, 2016

@andiyudistira @i5on9i A new update is out (0.6.47) with the fix. Can you confirm that the issue is fixed for you?

@i5on9i
Copy link

i5on9i commented Oct 27, 2016

cool~ it works well , thanks @ramya-rao-a

@andiyudistira
Copy link
Author

Cool, it works fine now thanks @ramya-rao-a 👍

@ramya-rao-a
Copy link
Contributor

Glad you are unblocked, happy coding!

@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

4 participants