# Improve panic message usefulness on local dev builds \(\#2819\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/5e9f7f10c079253dfd7b0baf3f07dcbb12d408e7)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 5e9f7f10c079253dfd7b0baf3f07dcbb12d408e7

Requested commit: 5e9f7f10c079253dfd7b0baf3f07dcbb12d408e7

Commit: 5e9f7f10c079253dfd7b0baf3f07dcbb12d408e7

Tree: b67a815920a966dc59bf9caf9305156ffaebeb27

Author: Julia

Committer: GitHub

## Message

```
Improve panic message usefulness on local dev builds (#2819)

I got tired of having to hack in a panic hook bypass whenever I wanted a
backtrace with line numbers. Now a dev channel build will behave more
like the default panic hook, printing a pretty traditional backtrace
message and exit with an error code instead of aborting to avoid the
annoying "Zed crashed" dialog.

I have plans to modify our panic reporting to be able to have line
numbers reported without breaking the de-duping but I haven't done that
yet.

Additionally I slightly improved what we do in threads which panic as a
result of another thread's panic.

Release Notes:

- N/A
```

## Parents

- [eb26fb2d45357e35d7d39edb8e2b3c6e0c1e9dbb](https://git.cafe/gitcafe/zed/commit/eb26fb2d45357e35d7d39edb8e2b3c6e0c1e9dbb?format=markdown)

- [3cee181f99c6de5ae264a119124d0ca94c0ffe3d](https://git.cafe/gitcafe/zed/commit/3cee181f99c6de5ae264a119124d0ca94c0ffe3d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/5e9f7f10c079253dfd7b0baf3f07dcbb12d408e7?format=markdown)