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
I'm trying to debug https://github.com/gokcehan/lf and I was hoping I could get some help here. It feels though as if there is a bug in vim-delve but I'm not experienced enough in bare dlv so I'm not sure.
Using Neovim, I open a source file in one split and in another I open a Neovim's :terminal in which I run dlv --headless. It looks like that:
The problem is, that when dlv --headless --listen localhost:1956 debug . is running, executing in Neovim :DlvConnect localhost:1956 seems to be making the other dlv process receive a continue command. If I don't have any breakpoints set, the debugger prompt is not usable while the debugged program is running.
Unsurprisingly, this doesn't happen when I run in a different terminal dlv connect localhost:1956.
Is this automatic continue behaviour intentional?
The text was updated successfully, but these errors were encountered:
Hey,
I'm trying to debug https://github.com/gokcehan/lf and I was hoping I could get some help here. It feels though as if there is a bug in vim-delve but I'm not experienced enough in bare
dlv
so I'm not sure.Using Neovim, I open a source file in one split and in another I open a Neovim's
:terminal
in which I rundlv --headless
. It looks like that:The problem is, that when
dlv --headless --listen localhost:1956 debug .
is running, executing in Neovim:DlvConnect localhost:1956
seems to be making the otherdlv
process receive acontinue
command. If I don't have any breakpoints set, the debugger prompt is not usable while the debugged program is running.Unsurprisingly, this doesn't happen when I run in a different terminal
dlv connect localhost:1956
.Is this automatic
continue
behaviour intentional?The text was updated successfully, but these errors were encountered: