# Remove legacy panic handling \(\#37947\) · gitcafe/zed

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

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

Visibility: public

Requested revision: a33af4e9c0c5276cae6f673323714801084d65ea

Requested commit: a33af4e9c0c5276cae6f673323714801084d65ea

Commit: a33af4e9c0c5276cae6f673323714801084d65ea

Tree: 8a1be3c42bd9b8dc802c3e4a0bef051f44ad3011

Author: Julia Ryan

Committer: GitHub

## Message

```
Remove legacy panic handling (#37947)

@maxdeviant We can eventually turn down the panic telemetry endpoint,
but should probably leave it up while there's still a bunch of stable
users hitting it.

@maxbrunsfeld We're optimistic that this change also fixed the macos
crashed-thread misreporting. We think it was because the
`CrashContext::exception` was getting set to `None` only on macos, while
on linux it was getting a real exception value from the sigtrap. Now
we've unified and it uses `SIGABRT` on both platforms (I need to double
check that this works as expected for windows).

We unconditionally set `RUST_BACKTRACE=1` for the current process so
that we see backtraces when running in a terminal by default. This
should be fine but I just wanted to note it since it's a bit abnormal.

Release Notes:

- N/A

---------

Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
```

## Parents

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

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