Support RUST_BACKTRACE
#2187
Assignees
Comments
szokeasaurusrex
added a commit
that referenced
this issue
Oct 22, 2024
The `anyhow` crate we use for error handling adds stack backtraces errors whenever [certain standard environment variables](https://doc.rust-lang.org/std/backtrace/index.html#environment-variables) are set (e.g. when `RUST_BACKTRACE=1`). Modify our error-printing logic to include these stack backtraces when printing errors that crash Sentry CLI, so that users can add this information to bug reports. Closes #2187
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because of the logic to exit Sentry CLI with a specific code, backtraces are not printed by default in Sentry CLI. This makes it harder to debug issues, since we don't always know where in code an error originates from. With
RUST_BACKTRACEsupport, we can instruct users experiencing errors to set the environment variable.Changes likely need to be made here:
sentry-cli/src/commands/mod.rs
Line 352 in df403cd
The text was updated successfully, but these errors were encountered: