![]() This adds a new `--client-addr=host:port` flag to `dlv dap`. If it is supplied, the dap process will dial into the tcp port where a DAP client is waiting, and work with only the DAP client. The DAP client is supposed to start the normal DAP message exchange starting with the 'initialize' request after the dlv dap process dials in and the connection is set up. VS Code Go extension plans to use this mode for * reliably detecting `dlv dap` readiness. Currently it depends on watching the log stream. After this PR, it can listen on a network port. * running `dlv dap` from any terminal (part of RunInTerminal workflow implementation). |
||
---|---|---|
.. | ||
dlv_attach.md | ||
dlv_backend.md | ||
dlv_connect.md | ||
dlv_core.md | ||
dlv_dap.md | ||
dlv_debug.md | ||
dlv_exec.md | ||
dlv_log.md | ||
dlv_redirect.md | ||
dlv_replay.md | ||
dlv_run.md | ||
dlv_test.md | ||
dlv_trace.md | ||
dlv_version.md | ||
dlv.md | ||
README.md |
Using Delve
You can invoke Delve in multiple ways, depending on your usage needs. Delve makes every attempt to be user-friendly, ensuring the user has to do the least amount of work possible to begin debugging their program.
Refer to the main usage document to further explore commands.