1---
 2title: Debugging Crashes
 3description: "Guide to debugging crashes for Zed development."
 4---
 5
 6# Debugging Crashes
 7
 8When Zed panics or crashes, it sends a message to a sidecar process that inspects the editor's memory and creates a [minidump](https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/getting_started_with_breakpad.md#the-minidump-file-format) in `~/Library/Logs/Zed` or `$XDG_DATA_HOME/zed/logs`. You can use this minidump to generate backtraces for all thread stacks.
 9
10If telemetry is enabled, Zed uploads these reports when you restart the app. Reports are sent to a [Slack channel](https://zed-industries.slack.com/archives/C0977J9MA1Y) and to [Sentry](https://zed-dev.sentry.io/issues) (both are Zed-staff-only).
11
12These crash reports include useful data, but they are hard to read without spans or symbol information. You can still analyze them locally by downloading source and an unstripped binary (or separate symbols file) for your Zed release, then running:
13
14```sh
15zstd -d ~/.local/share/zed/<uuid>.dmp -o minidump.dmp
16minidump-stackwalk minidump.dmp
17```
18
19Alongside the minidump in your logs directory, you should also see a `<uuid>.json` file with metadata such as the panic message, span, and system specs.
20
21## Using a Debugger
22
23If you can reproduce the crash consistently, use a debugger to inspect program state at the crash point.
24
25For setup details, see [Using a debugger](./debuggers.md#debugging-panics-and-crashes).