this post was submitted on 20 Mar 2026
10 points (100.0% liked)

Rust Programming

9206 readers
8 users here now

founded 7 years ago
MODERATORS
 

Always had the problem that if I wanted to just log an error, rather than bubble it all the way up to main(), that you wouldn't get a stacktrace. You could iterate the source chain and plug the stacktrace together yourself, but it's rather complex code.

Now I realized, you can do this to get a stacktrace:

let error = todo!("Get an error somehow...");
let error = anyhow::anyhow!(error); //converts to an `anyhow::Error`
eprintln!("Error with stacktrace: {error:?}");

For converting to an anyhow::Error, it often also makes sense to use anyhow::Context like so:

use anyhow::Context;
let error = error.context("Deleting file failed.");
you are viewing a single comment's thread
view the rest of the comments
[–] TehPers@beehaw.org 1 points 4 days ago

The error returns a stack trace like this because if you return Err(anyhow::Error) from your main function, it debug prints the error when it exits.

As you mentioned, it's very convenient during logging! The Display impl shows much less information, so usually you want the Debug info of anyhow::Error during logging.