Merge of rust-lang/backtrace-rs#757: [AIX] Update backtrace to account for libc changes and fix XCOFF parsing This patch synchronizes AIX backtrace support with newer libc updates and fix type correctness issues: - Bump libc to 0.2.175 to pick up latest AIX-related fixes. - Update libc::loadquery buffer argument to use *mut c_void instead of *mut c_char, matching the current libc API. - Fix XCOFF section name comparison to handle Option<&[u8]>.
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.