You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do some custom backtrace stuff in our panic hook (the relevant details being in panic.rs) and I don't really like the current output. It's very noisy, especially with printing the address of a frame even if we symbolicated it. That said I need to test it out in "production" environments where symbols are worse (no local debuginfo sitting in target/) to figure out what can be trimmed or not.
We do some custom backtrace stuff in our panic hook (the relevant details being in panic.rs) and I don't really like the current output. It's very noisy, especially with printing the address of a frame even if we symbolicated it. That said I need to test it out in "production" environments where symbols are worse (no local debuginfo sitting in target/) to figure out what can be trimmed or not.
The situation isn't 1:1 (not using the backtrace crate) but minidump_processor has much prettier output with this more complex impl: https://github.com/rust-minidump/rust-minidump/blob/main/minidump-processor/src/process_state.rs#L737
The text was updated successfully, but these errors were encountered: