2c1a822632
* proc/core: off-by-one error reading ELF core files core.(*splicedMemory).ReadMemory checked the entry interval erroneously when dealing with contiguous entries. * terminal,service,proc/*: adds dump command (gcore equivalent) Adds the `dump` command that creates a core file from the target process. Backends will need to implement a new, optional, method `MemoryMap` that returns a list of mapped memory regions. Additionally the method `DumpProcessNotes` can be implemented to write out to the core file notes describing the target process and its threads. If DumpProcessNotes is not implemented `proc.Dump` will write a description of the process and its threads in a OS/arch-independent format (that only Delve understands). Currently only linux/amd64 implements `DumpProcessNotes`. Core files are only written in ELF, there is no minidump or macho-o writers. # Conflicts: # pkg/proc/proc_test.go |
||
|---|---|---|
| .. | ||
| 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.