-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make backtrace output more end-user friendly #307
Comments
Could this be related to @shepmaster's recent changes in #306? To the best of my knowledge, SNAFU does not take advantage of |
Hmm, I don't have a great answer to the why, but the good news is that soon this will become moot: use snafu::prelude::*;
#[derive(Debug, Snafu)]
struct NeatError {
backtrace: snafu::Backtrace,
}
fn main() {
println!("{}", NeatSnafu.build().backtrace);
}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if I compare the output of backtrace-rs and snafu, they differ in readability and verbosity:
Backtrace-rs:
Snafu:
What I precisly want to change is that after the function should be removed and the paths should be relative to project root, not the filesystem:
currently:
wanted:
Since you're using the backtrace backend I don't see why it behaves like it does, but maybe you could shine a light on this.
In addition (but I doubt that will happen soon) is to reduce the backtrace to the relevant part, e.g. I don't want first two frames to appear (and maybe the last few, that are part of
_start_lang
)The text was updated successfully, but these errors were encountered: