DLV-BACKEND(1)

πŸ’– DLV-BACKEND(1) πŸ’–

okay bestie, listen up β€” this is the General Commands Manual page for dlv-backend, aka the lil corner of Delve that spills all the tea about the --backend flag. no cap, it's short, it's sweet, it's giving "quick reference card that actually slaps." πŸŽ€


✨ NAME ✨

dlv-backend β€” literally just Help about the --backend flag. that's it. that's the whole job. 🫢


🌸 SYNOPSIS 🌸

dlv backend [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

so the --backend flag is the one that decides which backend Delve is gonna use. main character decision, fr fr. here are the possible values, no notes:

  • default β€” uses lldb on macOS, and native everywhere else. the chill "read the room" option. πŸ’…
  • native β€” Native backend. the homegrown one. πŸ’–
  • lldb β€” Uses lldb-server or debugserver. ✨
  • rr β€” Uses mozilla rr (https://github.com/mozilla/rr). the time-travel girlie. πŸ”₯

and some backends can be configured using environment variables, which is lowkey the best part:

  • DELVE_DEBUGSERVER_PATH specifies the path of the debugserver executable for the lldb backend
  • DELVE_RR_RECORD_FLAGS specifies additional flags used when calling rr record
  • DELVE_RR_REPLAY_FLAGS specifies additional flags used when calling rr replay
pro tip from me to you: env vars are forever (until your shell session ends), so set them somewhere sensible. πŸ™‚β€β†•οΈ that's just vibes, but like, true vibes.

⭐ OPTIONS ⭐

  • -h, --help[=false] β€” help for backend. the "wait what does this do again" button. iconic. πŸ‘‘

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones backend inherited from its parent command, so they're all still valid here. slay, genetics. 🧬

  • --accept-multiclient[=false] β€” Allows a headless server to accept multiple client connections via JSON-RPC or DAP.
  • --allow-non-terminal-interactive[=false] β€” Allows interactive sessions of Delve that don't have a terminal as stdin, stdout and stderr
  • --api-version=2 β€” Selects JSON-RPC API version when headless. The only valid value is 2. Can be reset via RPCServer.SetApiVersion. See Documentation/api/json-rpc/README.md.
  • --backend="default" β€” Backend selection (see 'dlv help backend').
  • --build-flags="" β€” Build flags, to be passed to the compiler. For example: --build-flags="-tags=integration -mod=vendor -cover -v"
  • --check-go-version[=true] β€” Exits if the version of Go in use is not compatible (too old or too new) with the version of Delve.
  • --disable-aslr[=false] β€” Disables address space randomization
  • --headless[=false] β€” Run debug server only, in headless mode. 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 with 'unix:' to 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="" β€” 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.
  • -r, --redirect=[] β€” Specifies redirect rules for target process (see 'dlv help redirect')
  • --wd="" β€” Working directory for running the program.

πŸ‘€ SEE ALSO πŸ‘€


and that's the whole page bestie, you ate it, periodt πŸ’…βœ¨

oh also, quick sign-off so the paperwork is cute and complete: this page was Auto generated by spf13/cobra, and it's dated Aug 2026. so if you're reading it from the future β€” hi, love that for you. πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from