Comments (2)
However we also manually reimplement our panic handler to give a custom backtrace, and this would be disabled by
RUST_LIB_BACKTRACE=0
I believe the intended way to handle this is that the custom panic handler needs to use Backtrace::force_capture()
(https://doc.rust-lang.org/1.75.0/std/backtrace/struct.Backtrace.html#method.force_capture). Then it is no longer sensitive to RUST_BACKTRACE
and RUST_LIB_BACKTRACE
, so you can use RUST_LIB_BACKTRACE=0
to only control non-panic error handling backtraces.
In the backtrace
crate, Backtrace::new()
is equivalent to std::backtrace::Backtrace::force_capture()
so you effectively arrived at this already as of shotover/shotover-proxy#1408.
from anyhow.
I realized that for my use case, I actually use https://crates.io/crates/backtrace instead of std::backtrace
.
The backtrace crate doesnt actually check RUST_LIB_BACKTRACE, so I can simply add:
if std::env::var("RUST_LIB_BACKTRACE").is_err() {
std::env::set_var("RUST_LIB_BACKTRACE", "0");
}
To disable anyhows backtraces when RUST_BACKTRACE=1.
This does still allow the user to manually force RUST_LIB_BACKTRACE=1 if they need to.
I'll leave this issue open as it does represent a possible user issue, it is not however an issue that I actually face, so feel free to close this issue.
from anyhow.
Related Issues (20)
- backtrace seems to only work with opt-level=0 HOT 5
- Error display inconsistent HOT 1
- Couldn't use with nom error HOT 2
- the following trait bounds were not satisfied: `(): anyhow::context::ext::StdError` HOT 1
- Use `#[track_caller]` to provide info on where the error was created HOT 1
- Allow source errors to expose their own context? HOT 1
- `build.rs` should not detect nightly feature HOT 11
- [Question] In `{:#?}` why is the outermost context called "caused by" and how is `Context` expected to be used? HOT 1
- `ensure!` macro implementation details HOT 8
- Nightly feature wrongly enabled on stable toolchain HOT 3
- Should `anyhow::Error::chain` return `dyn Error + Send + Sync` HOT 2
- Customize backtrace logic?
- `anyhow!(e)` doesn't preserve `source` for `&Error` HOT 1
- Default Ok-type to `()` in `anyhow::Result` typedef HOT 2
- Updating from version 1.0.76 breaks backtraces HOT 2
- Make backtrace support optional HOT 10
- Possible performance regression on Windows HOT 5
- as_ref() type must be known at this point
- Depending on `CARGO_ENCODED_RUSTFLAGS` may produce stale builds HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from anyhow.