| commit | 57c75298115cf36505725281b4f45f03dacfa290 | [log] [tgz] |
|---|---|---|
| author | Jubilee <workingjubilee@gmail.com> | Wed May 07 17:40:56 2025 -0700 |
| committer | GitHub <noreply@github.com> | Wed May 07 17:40:56 2025 -0700 |
| tree | 8b17acc55d5d9c83d2a24a70561c75485b7fb120 | |
| parent | 6c882eb11984d737f62e85f36703effaf34c2453 [diff] |
ci: remove binary size check (rust-lang/backtrace-rs#710) Remove the "binary size check" workflow because it is often broken and now and then makes me sit through a discussion about its security needs. These discussions always make me feel very silly. I originally hoped this CI job would be a useful part of assuring that we would not accidentally bloat binaries when backtrace merges into std. However, it feels like that is not achieved by this workflow and at some point it has definitely outweighed the cost of maintaining it. We can readd something if we find a better way to implement things which is notably less jank and gets less complaints.
A library for acquiring backtraces at runtime for Rust. This library aims to enhance the support of the standard library by providing a programmatic interface to work with, but it also supports simply easily printing the current backtrace like libstd's panics.
[dependencies] backtrace = "0.3"
To simply capture a backtrace and defer dealing with it until a later time, you can use the top-level Backtrace type.
use backtrace::Backtrace; fn main() { let bt = Backtrace::new(); // do_some_work(); println!("{bt:?}"); }
If, however, you'd like more raw access to the actual tracing functionality, you can use the trace and resolve functions directly.
fn main() { backtrace::trace(|frame| { let ip = frame.ip(); let symbol_address = frame.symbol_address(); // Resolve this instruction pointer to a symbol name backtrace::resolve_frame(frame, |symbol| { if let Some(name) = symbol.name() { // ... } if let Some(filename) = symbol.filename() { // ... } }); true // keep going to the next frame }); }
The backtrace crate is a core component of the standard library, and must at times keep up with the evolution of various platforms in order to serve the standard library's needs. This often means using recent libraries that provide unwinding and symbolication for various platforms. Thus backtrace is likely to use recent Rust features or depend on a library which itself uses them. Its minimum supported Rust version, by policy, is within a few versions of current stable, approximately “stable - 2”.
This policy takes precedence over versions written anywhere else in this repo.
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in backtrace-rs by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.