454491ce86
We occasionally receive bug reports from users of VSCode-go and GoLand. GoLand has its own way of capturing the packet exchange between itself and delve but VSCode-go (supposedly) doesn't. So far this hasn't been a problem since all bug reports were obvious bugs on the plugin or easy to reproduce without VSCode-go, but it might be helpful in the future to have a way to log the packet exchange between dlv and a frontend. This commit adds a --log-output option to enable logging of all rpc messages and changes service/rpccommon accordingly. |
||
|---|---|---|
| .. | ||
| commands.md | ||
| dlv_attach.md | ||
| dlv_connect.md | ||
| dlv_core.md | ||
| dlv_debug.md | ||
| dlv_exec.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.