backtrace-rs
backtrace-rs copied to clipboard
rust-lang
Backtraces in Rust
The comment says it is done only for the short format: https://github.com/rust-lang/backtrace-rs/blob/57c75298115cf36505725281b4f45f03dacfa290/src/capture.rs#L493-L496 Which matches the printing code in libstd. The actual code however does it for the full format: https://github.com/rust-lang/backtrace-rs/blob/57c75298115cf36505725281b4f45f03dacfa290/src/capture.rs#L501-L507
The documentation on `*_unsynchronized` functions states that they are unsafe because they are 'unsynchronized'. However, they do not state what kind of synchronization the caller is expected to perform. Looking...
Hard dependency on https://github.com/nagisa/rust_libloading/pull/169.
I see from the release tagged 0.3.75, the intended MSRV is meant to be 1.79, however crates.io is showing 1.82. https://crates.io/crates/backtrace/0.3.75 
## 🤖 New release * `backtrace`: 0.3.75 -> 0.3.76 (✓ API compatible changes) Changelog ## [0.3.76](https://github.com/rust-lang/backtrace-rs/compare/backtrace-v0.3.75...backtrace-v0.3.76) - 2025-05-08 ### Other - Merge of rust-lang/backtrace-rs#705: Add `optimize(size)` to some particularly large...
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
The commit tagged was https://github.com/rust-lang/backtrace-rs/commit/f8cc6ac9acc4e663ecd96f9bcf1ff4542636d1b9 for the 0.3.75 release, but release-plz generated a crates.io release of https://github.com/rust-lang/backtrace-rs/commit/e09b86e75343365642d1adb568dde589308b0d07 Interesting. Not sure if I intend to do anything about it.
An implementation or dl_iterate_phdr was added to Haiku in https://github.com/haiku/haiku/commit/908107a15f63582157c7094be7273dbfffa1003c a little over a year after Haiku support got added to backtrace-rs.
# Description While using the `backtrace::resolve_frame_unsynchronized` API it seems we are not going through signal handlers. Here is what I get when using the API, ``` Starting backtrace-rs unwinding... Frame:...
For https://github.com/rust-lang/rust/pull/135804 I want to make sure the backtrace is always making progress. On most platforms it's enough to check the stack pointer changes. However, on x86 msvc with `debuginfo=line-tables-only`...
This implements the runtime side of https://github.com/rust-lang/compiler-team/issues/818. - Extract a helper out of `find_frames` for iterating over a `LookupContinuation` - Make the type signature for `search_object_map` consistent across all platforms....
