Debugger when attached to a running process is using wrong file paths for some files #3537
Labels
Debug
Issues related to the debugging functionality of the extension.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
go version
to get version of Go from the VS Code integrated terminal.go version go1.22.5 linux/amd64
Run
gopls -v version
to get version of Gopls from the VS Code integrated terminal.Run
code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.v0.42.1
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"]
orgopls
prefixes.Describe the bug
VSCode debugger uses wrong paths for some files during remote attach debug session. This only happens with few files. Debugger some how assumes the file path is
pkg/rpc/pkg/rpc/context.go
while the actual file path ispkg/rpc/context.go
and it fails to locate the file.Steps to reproduce the behavior:
I'm not sure if there is an easy way to reproduce this but I can provide additional information as needed. Sharing launch.json file contents here:
Screenshots or recordings
pkg/server/tenant.go
where it works as expected:pkg/rpc/context.go
where it doesn't work as expected:The text was updated successfully, but these errors were encountered: