debug: dlv-dap remote attach doesn't recognize cwd/remotePath - should it? #1874
Labels
debug/remote
issues related to remote debugging support
Debug
Issues related to the debugging functionality of the extension.
Projects
Milestone
Once #1873 is in, using hello-world program from
hello
directory from vscode, set a breakpoint in the editor.Then start the dlv server from the symbolic link directory.
There are two ways to configure the path mapping with
"debugAdapter": "legacy"
that work:Both only
substitutePath
works with dlv-dap.@suzmue @hyangah
Should we use this as an opportunity to migrate the users from
remotePath
tosubstitutePath
, which is more powerful with multiple entries and newdlv config
support in dap, matches dlv terminal, and can be used when connecting todlv dap
servers as well. Or should we aim for backward compatibility and mapremotePath
+cwd
tosubstitutePath
for the user? If not, we should update package.json because it misleadingly says "If specified, becomes the first entry in substitutePath."Update: this doesn't matter for Cloud Code. They can easily update their configuration to use whatevere.
The text was updated successfully, but these errors were encountered: