Remote Attach fails to set a breakpoint if program is started with --continue option

[quoctruong]

Steps to Reproduce:

1. Start a remote program through dlv with --continue option (recently added to dlv through cmd/dlv: add --continue to continue process on launch/attach go-delve/delve#1585). For example:

dlv exec /app --continue --accept-multiclient --api-version=2 --headless --listen=:3000

2. Attach the VSCode Go Debugger and set a breakpoint.
3. Breakpoints won't get hit.

[nagstaku]

I would guess that maybe there is a mis-match of files on your local system to the remote system and that is why it's never hitting (or at least that is what I experienced recently).

the applicable settings I had to set were:
"remotePath": "/app/root/dir/",
"cwd": "${workspaceFolder}/app/root/dir"

Although you should also post the rest of your launch.json

The vscode debug experience seems very rough currently, it doesn't seem to indicate if it's even able to reach a debug host for instance (ie, the port isn't even open on the target system, and never even connects).

You can add:
"tracing": "verbose",

and examine its output to look for oddities. Also, if possible, consider adding tcpflow to your target system, and then running this while attempting to attach debuggers (this is how i initially found my problems). For an alpine based docker container:

apk add tcpflow
tcpflow -i any -c

(-i is interface, and -c is Console print. Print the contents of packets, without storing in a file.)

[quoctruong]

I actually have a PR (#2685) to fix this bug. It seems to happen because VSCode does not halt dlv before setting a breakpoint in this case.

[ramya-rao-a]

This should now be fixed in the latest version (0.11.5) of the extension