DLV-LOG(1)

💖 DLV-LOG(1) 💖

okay bestie, so this is the manual page for dlv-log, which lives in the General Commands Manual section of the dlv family — that's Delve, the Go debugger, in case you were wondering. It's literally just the help page for the logging flags. That's it. That's the whole girl. And she eats. 💅

---

✨ NAME ✨

dlv-log — help about logging flags. yes that's really all it is, and honestly? iconic of it.

---

🌸 SYNOPSIS 🌸

dlv log [flags]

---

🦋 DESCRIPTION 🦋

so here's the tea: logging is off by default, and you turn it on by passing the --log flag. then you use --log-output to pick which components are the ones actually yapping. two-step process, very demure, very mindful.

the argument you hand to --log-output has to be a comma separated list of component names, and you can only choose from these ones right here:

• debugger — logs debugger commands
• gdbwire — logs the connection to the gdbserial backend
• lldbout — copies output from debugserver/lldb straight to standard output
• debuglineerr — logs recoverable errors while reading .debug_line
• rpc — logs all the RPC messages
• dap — logs all the DAP messages
• fncall — logs the function call protocol
• minidump — logs minidump loading
• stack — logs stacktracer

and THEN, as if that wasn't enough, --log-dest is right there to tell you where the logs should actually get written. here's the little trick: if the argument is a number, it gets interpreted as a file descriptor. if it's not a number, it gets interpreted as a file path. she's flexible like that. also — plot twist — this option will also redirect the "server listening at" message in headless and dap modes. multitasking queen. 👑

---

🎀 OPTIONS 🎀

• -h, --help[=false] — help for log. it's giving "explain yourself".

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

bestie these ones aren't even hers, she borrowed them from her parent command, but you still need to know them, so:

• --accept-multiclient[=false] — lets a headless server accept multiple client connections via JSON-RPC or DAP. the more the merrier fr.
• --allow-non-terminal-interactive[=false] — allows interactive sessions of Delve that don't have a terminal as stdin, stdout and stderr. living dangerously, love that for you.
• --api-version=2 — selects the 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. she's picky and she's right.
• --disable-aslr[=false] — disables address space randomization.
• --headless[=false] — run 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 with 'unix:' to use a unix domain socket.
• --log[=false] — enable debugging server logging. the main character flag.
• --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. stranger danger, but make it security.
• -r, --redirect=[] — specifies redirect rules for target process (see 'dlv help redirect').
• --wd="" — working directory for running the program.

---

🌈 SEE ALSO 🌈

• dlv(1) — the whole fam. go say hi.

---

okay that's the page!! 💖 this was auto generated by spf13/cobra, dated Aug 2026, and girl. the robots really said "we'll write your docs for you" and honestly they ate. mwah. bye bestie, go log something safe 🫶✨