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
So I tried to connect to a running dlv dap, and it connects alright (after I hard-code the port), but then immediately I get that dlv exits with code 1. After reading nvim-dap docs, I figure this is due to the following:
So I fixed my problem by commenting out that executable section. It'd probably make sense to make this executable section depend on whether or not mode == "remote".
The text was updated successfully, but these errors were encountered:
From the README:
So I tried to connect to a running
dlv dap
, and it connects alright (after I hard-code the port), but then immediately I get thatdlv exits with code 1
. After readingnvim-dap
docs, I figure this is due to the following:nvim-dap-go/lua/dap-go.lua
Lines 69 to 81 in 6aa8816
As it turns out, if an
executable
attribute is set,mfussenegger/nvim-dap
will spawn that executable, even whenrequest = "attach"
. This is incognruent withmode = "remote"
. Docs: https://github.com/mfussenegger/nvim-dap/blob/580d6e526358afd0e4bba053e68fd59cf581a161/doc/dap.txt#L76-L78.So I fixed my problem by commenting out that
executable
section. It'd probably make sense to make thisexecutable
section depend on whether or notmode == "remote"
.The text was updated successfully, but these errors were encountered: