Answer: Release builds use the release profile which sets `profile.(release).debug` to `"limited"`, and `"limited"` strips type-level and variable-level debug info, so debuggers cannot resolve local variables. To get full debug info, compile with `cargo run --config 'profile.release.debug="full"'` or `cargo build --config 'profile.release.debug="full"'`, or change the root `Cargo.toml` to `debug = "full"`. Status: Overdue (check was due 2026-11-20T13:40:02Z and has not succeeded) Entry: tool/zed/troubleshooting/release-build-debug-info Revision: 1 Digest: sha256:d4ffcb45bad70d36 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:01:36Z Last changed: 2026-11-13T04:01:36Z Last verified: 2026-11-19T13:40:02Z Next check: 2026-11-20T13:40:02Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of default debug setting | limited | [1] | 2026-11-19 what limited strips | type-level and variable-level debug info | [1] | 2026-11-19 cargo run command | cargo run --config 'profile.release.debug="full"' | [1] | 2026-11-19 cargo build command | cargo build --config 'profile.release.debug="full"' | [1] | 2026-11-19 Cargo.toml setting | debug = "full" | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/development/debuggers.md". https://zed.dev/docs/development/debuggers.md Role: primary. Accessed: 2026-11-19T13:40:02Z Quote: "This is done by setting the `profile.(release).debug` field in the root `Cargo.toml` field to `"limited"`." (Supports: default debug setting) Quote: "In short, `"limited"` strips type-level and variable-level debug info." (Supports: what limited strips) Quote: "cargo run --config 'profile.release.debug="full"'" (Supports: cargo run command) Quote: "cargo build --config 'profile.release.debug="full"'" (Supports: cargo build command) Quote: "debug = "full"" (Supports: Cargo.toml setting) Snapshot SHA-256: 19efa72696a5ec0129818f03bbf251aab074c5a6d8e36cee2ad0aa854a69b07c (captured 2026-11-13T04:01:35Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:01:36Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:40:02Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:40:02Z Last attempt: 2026-11-19T13:40:02Z Notes and limitations: Extracted automatically from a single official source (section "Release build profile considerations"). Human-readable page: https://zed.dev/docs/development/debuggers.html Related: https://latestn.com/tool/zed/troubleshooting/remote-development-known-limitations What are the known limitations of Zed remote development? https://latestn.com/tool/zed/troubleshooting/report-asciidoc-issues Where do I report issues with the AsciiDoc extension in Zed? https://latestn.com/tool/zed/troubleshooting/report-editor-issues-github Where do I report bugs or issues about the Zed editor itself? https://latestn.com/tool/zed/troubleshooting/quick-cpu-flamechart-profiling How do I do a quick CPU profile of Zed with a flamechart? https://latestn.com/tool/zed/troubleshooting/racket-language-server-support Does Zed support the Racket language server? https://latestn.com/tool/zed/troubleshooting/refresh-kernelspecs How do I refresh kernelspecs in Zed after installing a new kernel? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:01:36Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/release-build-debug-info/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/troubleshooting/release-build-debug-info POST: https://latestn.com/dispute/tool/zed/troubleshooting/release-build-debug-info with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/release-build-debug-info?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why can't I see local variables when debugging a release build of Zed, and how do I get full debug info? Revision 1, last verified 2026-11-19T13:40:02Z. https://latestn.com/tool/zed/troubleshooting/release-build-debug-info (accessed 2026-11-21T10:01:13Z). @misc{LatestN_tool_zed_troubleshooting_release_build_debug_info_r1, title = {Why can't I see local variables when debugging a release build of Zed, and how do I get full debug info?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/release-build-debug-info}}, note = {Revision 1; digest sha256:d4ffcb45bad70d36; last verified 2026-11-19T13:40:02Z; accessed 2026-11-21T10:01:13Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/troubleshooting/release-build-debug-info