backtrace-rs
backtrace-rs copied to clipboard
rust-lang
Backtraces in Rust
Since https://github.com/rust-lang/rust/pull/120593, 21 is the minimum supported API level so we can remove `dl_iterate_phdr` feature. Related https://github.com/android/ndk/wiki/Changelog-r26 https://github.com/rust-lang/rust/pull/129305 This pr mainly change 1. remove `dl_iterate_phdr` feature. 2. remove `cc` build...
According to addr2line's Cargo.toml the MSRV remains unchanged and all tests pass here.
This is part of the https://github.com/rust-lang/rust/pull/127897 work. This fix resolves the following failing unit tests: ``` [ui] tests/ui/backtrace/backtrace.rs [ui] tests/ui/backtrace/dylib-dep.rs [ui] tests/ui/backtrace/line-tables-only.rs [ui] tests/ui/backtrace/std-backtrace.rs [ui] tests/ui/panics/issue-47429-short-backtraces.rs#legacy [ui] tests/ui/panics/issue-47429-short-backtraces.rs#v0 [ui] tests/ui/panics/runtime-switch.rs#legacy...
This synchronizes the API definitions with std. Trouble is, std uses its own definition of the `windows_targets::link!` macro so I've used a path hack to include it in this crate...
Per @workingjubilee [comment](https://github.com/rust-lang/backtrace-rs/pull/649#issuecomment-2266257642)
As @workingjubilee [mentioned](https://github.com/rust-lang/backtrace-rs/pull/626#issuecomment-2134245457), `no one is really paying for professional maintenance of backtrace-rs`, so might as well try to do some volunteer upkeep. Just to keep things tidy. Note that...
Run ```shell cargo +nightly -Z unstable-options update --breaking cargo update ```
This should hopefully help avoid problems like this: https://github.com/rust-lang/backtrace-rs/actions/runs/10199897506/job/28218129515
The standard library recently gained a [`windows_raw_dylib` feature](https://github.com/rust-lang/rust/blob/c0e32983f5b06a6f7d8cc776ccac71de6512ed6d/library/std/Cargo.toml#L119) that enables building rust programs without any Windows SDK import libraries (though it still needs C/C++ runtime stuff). However, backtrace doesn't yet...