You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I set a breakpoint in the Delve window then code execution halts as expected. However, if I set the same breakpoint using :DlvAddBreakpoint it doesn't.
Looking at my application logs I can see the debug server is creating the breakpoint when using the Delve window e.g. created breakpoint: &api.Breakpoint{ID:1...} but not when setting it in the editor. So I assume the command is not sent when using the editor.
This is when connecting to a debug server running in a Docker container using :DlvConnect localhost:2345 apiVersion=2.
This is using:
Mac OS 10.12.6
NVIM v0.3.1
Delve 1.0.0-rc.2
The text was updated successfully, but these errors were encountered:
This is certainly an issue. The commands should be sent using the Delve connection instead of being issued directly. I won't have time to look into this right now. Any PRs for this are most welcome.
I don't know if it's fixed or not, new vim-delve user here, but I encounter the same problem, when I add the breakpoint from editor, it didn't stop at the newly assigned breakpoint. I need close the terminal buffer and reconnect delve for it to works. So perhaps for anyone encountering it, it might be a workaround for you 😁
If I set a breakpoint in the Delve window then code execution halts as expected. However, if I set the same breakpoint using
:DlvAddBreakpoint
it doesn't.Looking at my application logs I can see the debug server is creating the breakpoint when using the Delve window e.g.
created breakpoint: &api.Breakpoint{ID:1...}
but not when setting it in the editor. So I assume the command is not sent when using the editor.This is when connecting to a debug server running in a Docker container using
:DlvConnect localhost:2345 apiVersion=2
.This is using:
Mac OS 10.12.6
NVIM v0.3.1
Delve 1.0.0-rc.2
The text was updated successfully, but these errors were encountered: