Alex Crichton
Alex Crichton
> where as the builtin backtrace printer for the default provided panic hook has no such issues Hm can you clarify what the default here is? Do you mean that...
Hm scratch that ``` RUST_BACKTRACE=1 CARGO_PROFILE_DEV_PANIC=abort cargo run --example backtrace ``` in this repository on macOS prints nothing for this crate itself, but libstd prints a backtrace for the panic!...
Some quick investigation (heading out now, will dig in more later), is that this is related to how the library that generates the backtrace is itself compiled. In your code,...
Oh sorry so to clarify `CARGO_PROFILE_DEV_PANIC=abort` is just an alternate way of settting the profile in `Cargo.toml`, they do the same thing. It's just easier to gist snippets using CLI...
Oh I'm happy to provide advice/help/review, but unfortunately I don't have time to implement this myself. Feel free to take it on if you'd like!
Sure yeah! It looks like there's a custom-target-spec option called `requires_uwtable` which presumably forcibly generates unwind tables for a target. I think we'll want to basically promote that to a...
Oh wow, thanks @tmandry for pointing that out! I completely forgot that existed... I think that this issue may be mostly done in that case? Although it may be good...
I've tried to add some documentation for this in https://github.com/rust-lang/backtrace-rs/pull/407
Seems reasonable to me!
I don't believe this is related to gimli because gimli isn't used in libstd. That being said that still sounds like a regression that's likely related to this crate! (just...