delve/pkg/proc/native/dump_linux_other.go

//go:build linux && !amd64

package native

import (
	"github.com/go-delve/delve/pkg/elfwriter"
)

func (p *nativeProcess) DumpProcessNotes(notes []elfwriter.Note, threadDone func()) (threadsDone bool, out []elfwriter.Note, err error) {
	return false, notes, nil
}
fmt code (#2826) 2021-12-13 18:25:23 +00:00			`//go:build linux && !amd64`
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 21:39:33 +00:00
			`package native`

			`import (`
			`"github.com/go-delve/delve/pkg/elfwriter"`
			`)`

			`func (p *nativeProcess) DumpProcessNotes(notes []elfwriter.Note, threadDone func()) (threadsDone bool, out []elfwriter.Note, err error) {`
			`return false, notes, nil`
			`}`