Answer: To debug Go packages, set the Delve mode to "debug" with "program" set to the package name; to debug Go tests, set the Delve mode to "test" with "program" still the package name, using "buildFlags" for tags and "args" for test binary args. You can also run debugger: start (f4|f4) for zero-configuration debugging of Go tests and entry points.
Status: Overdue (check was due 2026-11-20T13:42:11Z and has not succeeded)
Entry: tool/zed/troubleshooting/debug-go-packages-tests
Revision: 1
Digest: sha256:d9bd3b867ffaf185 (changes whenever the content changes)
Timeline:
Created: 2026-11-13T04:03:42Z
Last changed: 2026-11-13T04:03:42Z
Last verified: 2026-11-19T13:42:11Z
Next check: 2026-11-20T13:42:11Z
Check interval: Daily
Expected change: No fixed schedule
Data:
Field | Value | Source | As of
package debug mode | debug | [1] | 2026-11-19
package program setting | package name | [1] | 2026-11-19
test debug mode | test | [1] | 2026-11-19
test program setting | package name | [1] | 2026-11-19
zero-config shortcut | debugger: start | [1] | 2026-11-19
debug config file | .zed/debug.json | [1] | 2026-11-19
Sources:
[1] Zed Industries. "zed.dev/docs/languages/go.md". https://zed.dev/docs/languages/go.md
Role: primary. Accessed: 2026-11-19T13:42:11Z
Quote: "To debug a specific package, you can do so by setting the Delve mode to "debug"." (Supports: package debug mode)
Quote: "In this case "program" should be set to the package name." (Supports: package program setting)
Quote: "To debug the tests for a package, set the Delve mode to "test"." (Supports: test debug mode)
Quote: "The "program" is still the package name" (Supports: test program setting)
Quote: "Run debugger: start (f4|f4) to see a contextual list of these preconfigured debug tasks." (Supports: zero-config shortcut)
Quote: "For more control, you can add debug configurations to `.zed/debug.json`." (Supports: debug config file)
Snapshot SHA-256: 49d9dbada0c59ae805a81b1a361faa2b107e4347f69520df65d293165ee408b4 (captured 2026-11-13T04:03:41Z)
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:03:42Z, so the values verified then were kept.
Cross-check: not-available at 2026-11-19T13:42:11Z. No independent second source is configured for this entry
Last successful check: 2026-11-19T13:42:11Z
Last attempt: 2026-11-19T13:42:11Z
Notes and limitations:
Extracted automatically from a single official source (section "Debugging").
Human-readable page: https://zed.dev/docs/languages/go.html
Related:
https://latestn.com/tool/zed/troubleshooting/debug-javascript-node How do I set up debugging for JavaScript files with Node in Zed?
https://latestn.com/tool/zed/troubleshooting/debug-panics-crashes How do I debug panics and crashes in Zed?
https://latestn.com/tool/zed/troubleshooting/debug-php How do I debug PHP in Zed?
https://latestn.com/tool/zed/troubleshooting/crash-minidump-location Where does Zed store crash minidump files?
https://latestn.com/tool/zed/troubleshooting/damaged-warning-fix How do I fix Zed showing a damaged warning or not opening on macOS?
https://latestn.com/tool/zed/troubleshooting/debug-external-agent How do I debug an external agent in Zed?
https://latestn.com/tool/ All entries in AI tools
Change log:
Time | Event | Change | Source
2026-11-13T04:03:42Z | added | Entry created | —
Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/debug-go-packages-tests/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/debug-go-packages-tests
POST: https://latestn.com/dispute/tool/zed/troubleshooting/debug-go-packages-tests with claim, evidence_url, and optionally field and contact (form-encoded or JSON)
GET: https://latestn.com/dispute/tool/zed/troubleshooting/debug-go-packages-tests?claim={what is wrong}&evidence_url={link}
How to cite:
LatestN. (2026). How do I debug Go packages or Go tests in Zed? Revision 1, last verified 2026-11-19T13:42:11Z. https://latestn.com/tool/zed/troubleshooting/debug-go-packages-tests (accessed 2026-11-21T09:59:50Z).
@misc{LatestN_tool_zed_troubleshooting_debug_go_packages_tests_r1,
title = {How do I debug Go packages or Go tests in Zed?},
author = {{LatestN}},
year = {2026},
howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/debug-go-packages-tests}},
note = {Revision 1; digest sha256:d9bd3b867ffaf185; last verified 2026-11-19T13:42:11Z; accessed 2026-11-21T09:59:50Z}
}
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/debug-go-packages-tests