DLV-CORE(1)
π NAME π
okay so bestie, welcome to dlv-core β it's the dlv command that lets you examine a core dump. fr fr that's the whole vibe. π«Ά
β¨ SYNOPSIS β¨
dlv core [flags]
π¦ DESCRIPTION π¦
Examine a core dump β and heads up, it only supports linux and windows core dumps. that's the boundary, no cap. π
so like, the core command opens up the core file you point it at π plus the executable that goes with it, and then it lets you poke around the state of the process exactly as it was when the core dump got taken. it's giving time capsule honestly πβ¨
here's the tea on what's supported, lowkey important:
linux/amd64core files πlinux/arm64core files πwindows/amd64minidumps πΈ- core files generated by Delve's own
dumpcommand π©·
periodt, that's the list. π
π OPTIONS π
-h,--help[=false]β help for core π₯Ί (yes it's just the help flag, she's simple, she's iconic)
π OPTIONS INHERITED FROM PARENT COMMANDS π
these babies come from the parent command, so they're not core's alone β they're family money πΈβ¨
--accept-multiclient[=false]β lets a headless server accept multiple client connections via JSON-RPC or DAP. the more the merrier, honestly π«--allow-non-terminal-interactive[=false]β allows interactive sessions of Delve that don't have a terminal as stdin, stdout and stderr. no tty, no problem π--api-version=2β picks the JSON-RPC API version when headless. the only valid value is2β like, that's it, that's the only one, don't try it. it can be reset viaRPCServer.SetApiVersion. seeDocumentation/api/json-rpc/README.mdπ--backend="default"β backend selection (check out'dlv help backend'for the deets) π§--build-flags=""β build flags, and they get passed straight to the compiler. example time:--build-flags="-tags=integration -mod=vendor -cover -v"π₯--check-go-version[=true]β exits if the version of Go in use isn't compatible with the version of Delve β too old or too new, she has standards, she's not picky she's just β¨ correct β¨--disable-aslr[=false]β disables address space randomization π²π«--headless[=false]β run the debug server only, in headless mode. the server will accept both JSON-RPC or DAP client connections π»--init=""β init file, executed by the terminal client π-l,--listen="127.0.0.1:0"β debugging server listen address. prefix it with'unix:'if you wanna use a unix domain socket π--log[=false]β enable debugging server logging π--log-dest=""β writes logs to the specified file or file descriptor (see'dlv help log') π--log-output=""β a comma separated list of components that should produce debug output (see'dlv help log') π§Ύ--only-same-user[=true]β only connections from the same user that started this instance of Delve are allowed to connect. stranger danger π«π-r,--redirect=[]β specifies redirect rules for target process (see'dlv help redirect') π--wd=""β working directory for running the program π
π SEE ALSO π
dlv(1)β the main character, go say hi π
and that's the whole page bestie, you ate it, no crumbs left π β¨
this lil doc was Auto generated by spf13/cobra back in Aug 2026, and it lives at the top of the page as DLV-CORE(1) β General Commands Manual energy, iconic behavior, mwah ππ¦π
π¦ where this page comes from
- ubuntu stonking: delve 1.27.1-4 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms