go - 如何使用 VSCode 远程调试 Go 代码

Question

我在需要调试的 docker 容器中运行一个进程。该过程在 docker 的入口点通过dlv debug /go/src/path/to/package --headless --listen=:2345 --log以便稍后在 VSCode 中启用调试。

docker 容器通过以下方式启动docker run --rm -it -p 2345:2345 my_image:tag .注意 delve 的端口是公开的。

在 VSCode 中，我定义了 launch.json如下:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Attach remote",
            "type": "go",
            "request": "attach",
            "mode": "remote",
            "port": 2345,
            "host": "127.0.0.1",
            "apiVersion": 1
        }
    ]
}

启动“附加远程”VSCode 调试配置后，我得到


它不是很清楚，但该 UI 使我相信我现在已连接到远程 headless 调试器并准备进行调试。我定义了一个断点，我知道它会被我可以发送远程进程的请求击中。我发出那个请求，得到结果，断点一直没有命中，说明我还没有实现远程调试。

我的 VSCode“附加远程”配置有问题吗？我可以用 dlv connect :2345 进行命令行调试并且实际上调试远程进程就好了，这表明 headless 服务器可以正常工作。我宁愿在 VSCode 中使用源代码进行调试。

Answer 1

用 latest beta of vscode-go 再试一次(2020年4月)(2020年4月之后的任何时候，最新的官方vscode-go版本就足够了)
Microsoft/vscode-go issue 2010包括来自 Ramya Rao 的确认:

The fix from #3108 is available in the latest beta version of this extension. Please do try and share feedback
The latest version of the extension now has the fix to this issue

和:

I can confirm that I am able to hit breakpoints now using AWS SAM to launch a linux container with delve and go binaries compiled from Windows.

For anyone still having this problem (like I was before I edited this comment), take care that the "remotePath" element of your launch.json is the absolute path to the source files as compiled on your local system (not the container).
As implied above - it's the absolute local path that is added to the DWARF compilation unit file table when you compile the binary.