-
Notifications
You must be signed in to change notification settings - Fork 797
Couldn't start dlv dap: Error: No available ports found #3756
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
Comments
Hi @Aatroy, Thanks for reporting the issue. I was not able to re-produce the issue you encountered. My experience is normally smooth. See Looks like the error happened even before the dlv is running. VSCode-Go uses the "get-port" ( The version we are using is pretty old though. But I do not find a lot diff between the v5.1.1 and the v7.1.0 (latest). Could you check if there is port available in your localhost though? I think this is not related to which code base you are trying to debug. |
I tested get-port function with this code in centos 6.3 and 7.5 getPort().then((port) => { |
how can i edit this file , I tried use |
You can follow the contributing guide here Once you download the repo, you can launch another vscode with the developing version of go extension. Then you can test the behavior of those functions. By default, the new vscode only have one extension (which is the developing version of go extension). You can make local modification for this file Thank you. |
{ // 使用 IntelliSense 了解相关属性。 // 悬停以查看现有属性的描述。 // 欲了解更多信息,请访问: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "main", "type": "go", "request": "launch", "mode": "debug", "cwd": "./", "program": "main.go", } ] }
launch.json like this.
when I run dlv in vscode debug , the command while execute
/usr/local/go/bin/dlv dap --listen=127.0.0.1:45863 --log-dest=3 from /projects/path
but some times , the Error happened . And I run debug repeatedly multiple times will solve the problem. How can I fundamentally solve such a problem?
The text was updated successfully, but these errors were encountered: