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 #1052

Closed
pschuegr opened this issue Jun 23, 2017 · 6 comments
Closed

Debug adapter process has terminated unexpectedly #1052

pschuegr opened this issue Jun 23, 2017 · 6 comments
Labels

Comments

@pschuegr
Copy link

pschuegr commented Jun 23, 2017

I'm having the same issue as this one from last year: #564. Unable to launch the debugger from within vscode go or I get "Debug adapter process has terminated unexpectedly" (twice).

package main

import (
	"fmt"
)

func main() {
	fmt.Println("hello world")
}
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch",
            "type": "go",
            "request": "launch",
            "mode": "debug",
            "remotePath": "",
            "port": 2345,
            "host": "127.0.0.1",
            "program": "${workspaceRoot}/main.go",
            "env": {},
            "args": [],
            "showLog": true
        }
    ]
}
  • OSX 10.12.5
  • vscode 1.13.1
  • vscode-go 0.6.62
  • dlv works fine from the command line
  • same issue with remote debugging
  • no output in debug console
@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Jun 28, 2017

Sorry, it took so long to respond.

Can you set "trace": "verbose" in the debug config and see if you get any logs in the debug console?

@pschuegr
Copy link
Author

Sorry, nothing else in the debug console with trace: "verbose"

@ramya-rao-a
Copy link
Contributor

Not even the initial lines about writing to a file?

screen shot 2017-06-28 at 8 24 17 pm

Have you been able to debug successfully before? Or never got it to work in your current environment? What I am trying to get at is if this is a regression due to a recent update or an environment issue.

cc @roblourens

@pschuegr
Copy link
Author

pschuegr commented Jun 29, 2017

@ramya-rao-a Nothing, unfortunately. I tested this on another machine and it seems to work fine, so it's definitely an environment thing. I'll dig into it more - do you have any suggestions?

I've confirmed that both machines are running Code 1.13.1, vscode-go 0.6.62, golang 1.8.3 darwin/amd64, and dlv 1.0.0-rc.1.

Edit: Thought the mock-debug adapter had some useful information, but that turned out to be false.
Edit2: I think there's something borked with my install - the package.json for the go extension points to ./out/src/debugAdapter/goDebug.js, which afaict doesn't exist. I'll try re-installing.

@pschuegr
Copy link
Author

pschuegr commented Jun 29, 2017

Reinstalled and the debugAdapter directory showed up fine. Thanks for your help.

@ramya-rao-a
Copy link
Contributor

go extension points to ./out/src/debugAdapter/goDebug.js, which afaict doesn't exist

That's a new one :)
No wonder the debug adapter couldn't start coz it didn't exist 😆

Glad you are unblocked now. 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
Projects
None yet
Development

No branches or pull requests

2 participants