Answer: After enabling full debug info and building with `cargo build`, run `rust-gdb` or `rust-lldb` against the compiled Zed binary, e.g. `rust-gdb target/debug/zed` or `rust-lldb target/debug/zed`. You can also attach to a running Zed process with `rust-gdb -p ` or `rust-lldb -p `. Status: Overdue (check was due 2026-11-20T13:40:03Z and has not succeeded) Entry: tool/zed/troubleshooting/shell-debugger-usage Revision: 1 Digest: sha256:cf329bfe7e08213d (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:03Z Next check: 2026-11-20T13:40:03Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of GDB command | rust-gdb target/debug/zed | [1] | 2026-11-19 LLDB command | rust-lldb target/debug/zed | [1] | 2026-11-19 GDB attach command | rust-gdb -p | [1] | 2026-11-19 LLDB attach command | rust-lldb -p | [1] | 2026-11-19 Build command | cargo build | [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:03Z Quote: "rust-gdb target/debug/zed" (Supports: GDB command) Quote: "rust-lldb target/debug/zed" (Supports: LLDB command) Quote: "rust-gdb -p " (Supports: GDB attach command) Quote: "rust-lldb -p " (Supports: LLDB attach command) Quote: "After enabling full debug info and building with `cargo build`" (Supports: Build command) 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:03Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:40:03Z Last attempt: 2026-11-19T13:40:03Z Notes and limitations: Extracted automatically from a single official source (section "Usage with Zed"). Human-readable page: https://zed.dev/docs/development/debuggers.html Related: https://latestn.com/tool/zed/troubleshooting/show-lsp-error-messages How do I show language server error messages in the Zed status bar? https://latestn.com/tool/zed/troubleshooting/verify-ocamllsp-installed How do I verify that ocamllsp is installed for Zed? https://latestn.com/tool/zed/troubleshooting/warn-slow-function How do I make Zed warn me when a function is slow? https://latestn.com/tool/zed/troubleshooting/run-visual-regression-tests How do I run Zed's visual regression tests on macOS? https://latestn.com/tool/zed/troubleshooting/rust-large-project-performance How do I configure rust-analyzer for large Rust projects to improve performance in Zed? https://latestn.com/tool/zed/troubleshooting/semantic-tokens-not-appearing Why are semantic tokens not appearing in Zed and how do I troubleshoot it? 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/shell-debugger-usage/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/shell-debugger-usage POST: https://latestn.com/dispute/tool/zed/troubleshooting/shell-debugger-usage with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/shell-debugger-usage?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I run Zed under GDB or LLDB from a shell? Revision 1, last verified 2026-11-19T13:40:03Z. https://latestn.com/tool/zed/troubleshooting/shell-debugger-usage (accessed 2026-11-21T09:52:51Z). @misc{LatestN_tool_zed_troubleshooting_shell_debugger_usage_r1, title = {How do I run Zed under GDB or LLDB from a shell?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/shell-debugger-usage}}, note = {Revision 1; digest sha256:cf329bfe7e08213d; last verified 2026-11-19T13:40:03Z; accessed 2026-11-21T09:52:51Z} } 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/shell-debugger-usage