Answer: The extension tries to find an `lldb-dap` binary using `swiftly`, using `xcrun`, and by searching `$PATH`, in that order of preference. It does not attempt to download `lldb-dap` if it's not found. Status: Overdue (check was due 2026-11-20T13:43:32Z and has not succeeded) Entry: tool/zed/troubleshooting/lldb-dap-binary-lookup Revision: 1 Digest: sha256:7c38b4a5d929bbae (changes whenever the content changes) Timeline: Created: 2026-11-13T04:05:03Z Last changed: 2026-11-13T04:05:03Z Last verified: 2026-11-19T13:43:32Z Next check: 2026-11-20T13:43:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Search order | using `swiftly`, using `xcrun`, and by searching `$PATH`, in that order of preference | [1] | 2026-11-19 Download behavior | doesn't attempt to download `lldb-dap` if it's not found | [1] | 2026-11-19 Adapter name | `Swift` | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/languages/swift.md". https://zed.dev/docs/languages/swift.md Role: primary. Accessed: 2026-11-19T13:43:32Z Quote: "The extension tries to find an `lldb-dap` binary using `swiftly`, using `xcrun`, and by searching `$PATH`, in that order of preference." (Supports: Search order) Quote: "The extension doesn't attempt to download `lldb-dap` if it's not found." (Supports: Download behavior) Quote: "Zed's name for the adapter (in the UI and `debug.json`) is `Swift`" (Supports: Adapter name) Snapshot SHA-256: b766cb6dda2a7f25452155b82778b76fa822f87db8e45ec5b0ead2d325065e5f (captured 2026-11-13T04:05:03Z) 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:05:03Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:43:32Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:43:32Z Last attempt: 2026-11-19T13:43:32Z Notes and limitations: Extracted automatically from a single official source (section "Debugging"). Human-readable page: https://zed.dev/docs/languages/swift.html Related: https://latestn.com/tool/zed/troubleshooting/makefile-extension-issues Where do I report issues with the Makefile extension in Zed? https://latestn.com/tool/zed/troubleshooting/missing-license-ci-failure What happens if a Zed extension has no valid license? https://latestn.com/tool/zed/troubleshooting/open-zed-log How do I open the Zed log to troubleshoot a problem? https://latestn.com/tool/zed/troubleshooting/graphics-issues-fails-to-launch How do I troubleshoot Zed failing to launch due to graphics issues on Windows? https://latestn.com/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling How do I do in-depth CPU tracing profiling of Zed? https://latestn.com/tool/zed/troubleshooting/julia-extension-issues Where do I report issues with the Zed Julia extension? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:05:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/lldb-dap-binary-lookup/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/lldb-dap-binary-lookup POST: https://latestn.com/dispute/tool/zed/troubleshooting/lldb-dap-binary-lookup with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/lldb-dap-binary-lookup?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Zed find the lldb-dap binary for Swift debugging? Revision 1, last verified 2026-11-19T13:43:32Z. https://latestn.com/tool/zed/troubleshooting/lldb-dap-binary-lookup (accessed 2026-11-21T09:58:10Z). @misc{LatestN_tool_zed_troubleshooting_lldb_dap_binary_lookup_r1, title = {How does Zed find the lldb-dap binary for Swift debugging?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/lldb-dap-binary-lookup}}, note = {Revision 1; digest sha256:7c38b4a5d929bbae; last verified 2026-11-19T13:43:32Z; accessed 2026-11-21T09:58:10Z} } 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/lldb-dap-binary-lookup