From cfb8cae29ca18c2c136bce43af01e019a89169a2 Mon Sep 17 00:00:00 2001 From: Tuur Vanhoutte <4633209+zjeffer@users.noreply.github.com> Date: Mon, 28 Apr 2025 17:33:19 +0200 Subject: [PATCH] docs: Fix linux crash logs location (#29444) Release Notes: - N/A --- docs/src/development/debugging-crashes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/development/debugging-crashes.md b/docs/src/development/debugging-crashes.md index dddc13237783dbdc87ab807d9963ab10eb5063e4..d08ab961cc927cc5c0922f3836706678fe09c61f 100644 --- a/docs/src/development/debugging-crashes.md +++ b/docs/src/development/debugging-crashes.md @@ -27,7 +27,7 @@ The output contains the source file and line number, and the demangled symbol in ## Panics -When the app panics at the rust level, Zed creates a file in `~/Library/Logs/Zed` or `$XDG_DATA_HOME/logs` with the text of the panic, and a summary of the backtrace. On boot, if you have telemetry enabled, we upload these panics so we can keep track of them. +When the app panics at the rust level, Zed creates a file in `~/Library/Logs/Zed` or `$XDG_DATA_HOME/zed/logs` with the text of the panic, and a summary of the backtrace. On boot, if you have telemetry enabled, we upload these panics so we can keep track of them. A panic is also considered a crash, and so for most panics we get both the crash report and the panic.