63a660820e
Going forward, all documentation should be placed in the Documentation directory in the root of the project. This switch allows maintainers to approve updates to documentation before they are committed, as opposed to the pre-existing wiki which anybody could modify. Currently the Documentation directory includes docs on building, usage, and minimal docs around the API. This is just the initial commit, and documentation will continue to improve over time. Some changes have been made (and will continue to be made) to `cmd/dlv` to ensure we can auto-generate documentation for all commands from the newly provided script `scripts/gen-usage-docs.go`, which can be invoked via `go run scripts/gen-usage-docs.go`. Additionally, version has been split into its own package. This was a bit of housekeeping related to the changes made the `cmd/dlv`. |
||
|---|---|---|
| .. | ||
| commands.md | ||
| dlv_attach.md | ||
| dlv_connect.md | ||
| dlv_debug.md | ||
| dlv_exec.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.