Remote debugging no longer stops at break points anymore after updating to v0.41.0

[krav-la]

Remote debugging no longer stops at break points anymore after updating to v0.41.0

[hyangah]

@krav-la Thanks for the report. This is caused by v0.41.0 using Delve DAP as the default debug adapter for remote debugging.

Is it possible for you to find the remote workspace, goroot, and module cache paths? If so, can you give a try to formulate the substitutePath configuration ? e.g.

{
    "name": "Connect to server", 
      ...
     "substitutePath": [
         {
             "from": "${workspaceFolder}", "to": "/remote/path/to/workspace",
             "from": "/local/path/to/gomodcache", "to": "/remote/path/to/gomodcache",
             "from": "/local/path/to/goroot", "to": "/remote/path/to/goroot", 
         },
     ]
}

/local/path/to/gomodcache can be found with go env GOMODCACHE.
/local/path/to/goroot can be found with go env GOROOT.

It will be nice if the VSCode Go extension or Delve can automate this mapping computation.

If this is too tricky, the last resort is to use the legacy debug adapter by adding "debugAdapter": "legacy" to the configuration.

[gm0stache]

-> related issue: #3096 (comment)

could you please link the two?

[sasklacz]

@krav-la Thanks for the report. This is caused by v0.41.0 using Delve DAP as the default debug adapter for remote debugging.

Is it possible for you to find the remote workspace, goroot, and module cache paths? If so, can you give a try to formulate the substitutePath configuration ? e.g.

{
    "name": "Connect to server", 
      ...
     "substitutePath": [
         {
             "from": "${workspaceFolder}", "to": "/remote/path/to/workspace",
             "from": "/local/path/to/gomodcache", "to": "/remote/path/to/gomodcache",
             "from": "/local/path/to/goroot", "to": "/remote/path/to/goroot", 
         },
     ]
}

/local/path/to/gomodcache can be found with go env GOMODCACHE. /local/path/to/goroot can be found with go env GOROOT.

It will be nice if the VSCode Go extension or Delve can automate this mapping computation.

If this is too tricky, the last resort is to use the legacy debug adapter by adding "debugAdapter": "legacy" to the configuration.

For me the legacy option didn't work. Also this fix works for my files but not the dependencies.

[suzmue]

We have decided to revert the change of the default back to using the legacy debug adapter for remote attach in v0.41.3 to give us time to address this breakpoint issue from a lack of automated path mapping (#3193). We will try to address the broken breakpoint in the dependency in dlv dap.

[gopherbot]

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.)

[gopherbot]

Change https://go.dev/cl/580019 mentions this issue: Revert "docs: update the debugging doc about remote mode default adapter"

[gopherbot]

Change https://go.dev/cl/580422 mentions this issue: Revert "docs: update the debugging doc about remote mode default adapter"