debug: "outside available modules" when use auto mode to debug at remote development

[Seumi]

For asking questions, see:

• Stack Overflow
• GitHub Discussions (Help)
• #vscode channel in Gophers Slack

Before filing an issue, please review our troubleshooting guides

• Troubleshooting problems with debugging
• Troubleshooting other problems

Please answer these questions before submitting your issue. Thanks!

What version of Go, VS Code & VS Code Go extension are you using?

• Run go version to get version of Go from the VS Code integrated terminal.
  • go version go1.16.7 linux/amd64
• Run gopls -v version to get version of Gopls from the VS Code integrated terminal.
  • Build info
    golang.org/x/tools/gopls v0.7.1
    golang.org/x/tools/gopls@v0.7.1 h1:Mh3Z8Xcoq3Zy7ksSlwDV/nzQSbjFf06A+L+F8YHq55U=
    github.com/BurntSushi/toml@v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
    github.com/google/go-cmp@v0.5.5 h1:Khx7svrCpmxxtHBq5j2mp/xVjsi8hQMfNLvJFAlrGgU=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/mod@v0.4.2 h1:Gz96sIWK3OalVv/I/qNygP42zyoKp3xptRVCWRFEBvo=
    golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c h1:5KslGYwFpkhGh+Q16bwMP3cOontH8FOep7tGV86Y7SQ=
    golang.org/x/sys@v0.0.0-20210510120138-977fb7262007 h1:gG67DSER+11cZvqIMb8S8bt0vZtiN6xWYARwirrOSfE=
    golang.org/x/tools@v0.1.6-0.20210802203754-9b21a8868e16 h1:ZC/gVBZl8poJyKzWLxxlsmhayVGosF4mohR35szD5Bg=
    golang.org/x/xerrors@v0.0.0-20200804184101-5ec99f83aff1 h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
    honnef.co/go/tools@v0.2.0 h1:ws8AfbgTX3oIczLPNPCu5166oBg9ST2vNs0rcht+mDE=
    mvdan.cc/gofumpt@v0.1.1 h1:bi/1aS/5W00E2ny5q65w9SnKpWEF/UIOqDYBILpo9rA=
    mvdan.cc/xurls/v2@v2.2.0 h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A=
• Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders.
  • 1.59.0
    379476f0e13988d90fab105c5c19e7abc8b1dea8
    x64
• Check your installed extensions to get the version of the VS Code Go extension
  • v0.27.0
• Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command.

Share the Go related settings you have added/edited

Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.

Describe the bug

When I use go mod init to initialize a module and write a simple main.go file, set a breakpoint at will, and then press F5 to start debugging. The console output：
Starting: /home/xxx/go/bin/dlv-dap dap --listen=127.0.0.1:11031 --log=true --log-dest=3
DAP server listening at: 127.0.0.1:11031
Build Error: go build -o /data00/home/xxx/go/src/xxx/tdebug/__debug_bin -gcflags all=-N -l /home/xx/go/src/xxx/tdebug
directory /home/xxx/go/src/xxx/tdebug outside available modules (exit status 1).
But when i execute this command manually(go build -o .....), the execution was successful and the file "__debug_bin" was generated.
Then i change the mode from "auto" to "exec" and specify the path of "__debug_bin", the debugging can start.

Steps to reproduce the behavior:

1. mkdir tdebug && cd tdebug
2. go mod init tdebug
3. write a main.go just contains print "hello world" and make a breakpoint
4. F5 to start debug
5. the error occurred

Screenshots or recordings

[Seumi]

go env
Workspace Folder (tdebug): /home/xxx/tdebug
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/xxx/.cache/go-build"
GOENV="/home/xxx/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/xxx/workspace/go/pkg/mod"
GONOPROXY="xxx"
GONOSUMDB="xxx"
GOOS="linux"
GOPATH="/home/xxx/workspace/go"
GOPRIVATE="xxx"
GOPROXY="xxx"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.google.cn"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.7"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/data00/home/xxx/workspace/go/src/xxx/tdebug/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2766144329=/tmp/go-build -gno-record-gcc-switches"

[hyangah]

@Seumi are you using symlink? It looks like the go command and the delve runs in /data00/home/xxx/workspace/go/src/xxx/tdebug not in /home/xxx/tdebug, so the go command got confused.
Can you check if you still see the problem if you open the code from /data00/home/xxx/workspace/go/src/xxx/tdebug folder ? Thanks!

[Seumi]

@Seumi are you using symlink? It looks like the go command and the delve runs in /data00/home/xxx/workspace/go/src/xxx/tdebug not in /home/xxx/tdebug, so the go command got confused.
Can you check if you still see the problem if you open the code from /data00/home/xxx/workspace/go/src/xxx/tdebug folder ? Thanks!

Thanks for your reply! @hyangah
Yeah, it just work when i open the project from /data00/xxx....
But i don't know why there is a "data00" here, it seem the go tool set this symlink automatically.
When i use "Locate Configured Go Tools", the go mod is "GOMOD=/data00/home/xxx..." but when i run go env in terminal, the go mod is "GOMOD=/home/xxx...", without "data00". So I want to know if this is a mechanism to go extend itself or a problem of my environment

[Seumi]

It is a problem in my environment. The system image has a symlink, /home/xxx ->/data00/home/xxx, and the go tool chain doesn't seem to recognize it😢

[gopherbot]

Change https://golang.org/cl/346095 mentions this issue: [release] src/goDebugConfiguration: massage launch config for debug/test