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/amd64 core files πŸ‘‘
  • linux/arm64 core files πŸ‘‘
  • windows/amd64 minidumps 🌸
  • core files generated by Delve's own dump command 🩷

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 is 2 β€” like, that's it, that's the only one, don't try it. it can be reset via RPCServer.SetApiVersion. see Documentation/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