-
Notifications
You must be signed in to change notification settings - Fork 760
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
Debug test fails to start #1637
Comments
Are you on MacOS? It looks like this is coming from the debugserver that dlv relies on as its backend on MacOS. |
yep M1 Mac |
What's your Without a test case to reproduce, we would need some additional logging to confirm that this is an upstream error.
|
By default you will get logging from dlv's debugger layer. If instead you use |
The launch config you shared resulted in the same error I have the latest delve |
with |
Sorry yes, here is the additional output:
|
There appears to be some kind of mismatch with your architecture and software installations: |
@dylankilkenny in addition to check the debugserver version, also check if your vscode for apple silicon or universal just in case. Long story: I heard apple has a "defaulting to x86 if any ancestor process is x86" policy so if the vscode (or vscode-insider) is not the right arch type, all the subprocesses (including debug adapter) will use a x86 version. As seen in #1087 and go-delve/delve#2332, previously we suggested to use a wrapper script to sort out this because there was no arm64 native version of vscode. But now VSCode officially supports arm64, so wrapper script should be necessary any more if the right version of VSCode is used. Thanks and let us know how it goes. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
I had to update the current version of Visual Studio Code to the new M1 Silicon version. Thanks much @hyangah! |
I got the same issues with macbook M1. VS Code and Go are ARM64 version. The debug logs are bellow. Please help me! Many thanks!
|
What version of Go, VS Code & VS Code Go extension are you using?
go version
to get version of Go from the VS Code integrated terminal.go1.16.6 darwin/arm64
gopls -v version
to get version of Gopls from the VS Code integrated terminal.golang.org/x/tools/gopls v0.7.0
code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.1.59.0-insider
v0.26.0
Go: Locate Configured Go Tools
command.go-outline: /Users/dylankilkenny/go/bin/go-outline installed
gotests: gotests not installed
gomodifytags: gomodifytags not installed
impl: impl not installed
goplay: goplay not installed
dlv: /Users/dylankilkenny/go/bin/dlv installed
dlv-dap: dlv-dap not installed
staticcheck: /Users/dylankilkenny/go/bin/staticcheck installed
gopls: /Users/dylankilkenny/go/bin/gopls installed
Share the Go related settings you have added/edited
Describe the bug
When clicking
debug test
the debug console produces the following outputSteps to reproduce the behavior:
debug test
for any testThe text was updated successfully, but these errors were encountered: