delve/Documentation/backend_test_health.md
Alessandro Arzilli 2c1a822632
terminal,service,proc/*: adds dump command (gcore equivalent) (#2173)
* 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
2021-01-29 13:39:33 -08:00

20 lines
512 B
Markdown

Tests skipped by each supported backend:
* 386 skipped = 2% (3/147)
* 1 broken
* 2 broken - cgo stacktraces
* arm64 skipped = 2% (3/147)
* 2 broken
* 1 broken - global variable symbolication
* darwin/lldb skipped = 0.68% (1/147)
* 1 upstream issue
* freebsd skipped = 7.5% (11/147)
* 11 broken
* linux/386/pie skipped = 0.68% (1/147)
* 1 broken
* pie skipped = 0.68% (1/147)
* 1 upstream issue - https://github.com/golang/go/issues/29322
* windows skipped = 1.4% (2/147)
* 1 broken
* 1 upstream issue