Jane Losare-Lusby

relevant thread https://github.com/rust-lang/project-error-handling/issues/23 I tend to agree with @BurntSushi here and stand by a similar comment I made towards the end of the above thread. > For now, the recommendation...

@alexcrichton some background I know that the default panic hook from `std` provides custom backtrace formatting machinery so that it can avoid needing to allocate, so my guess is that...

> It looks though like you're getting different output than I am for effectively the same example. You're on Linux, right? yea, but this is using stable and I'm not...

> (substituting the right target) I think that you'll see that libstd can't generate a backtrace either (or at least that's what I get locally). This makes me think that...

Oh okay, that makes a lot of sense, and a `-Cgenerate-unwind-tables` sounds very helpful. If you want / need any help implementing the feature I can contribute to this as...

> 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! totally understandable. And yea,...

> This option exists! [`-C force-unwind-tables`](https://doc.rust-lang.org/rustc/codegen-options/index.html#force-unwind-tables) oh my goddd tylerrrrr :heart:

Just wanted to go ahead and confirm that this worked for me, after enabling `force-unwind-tables` + panic = abort I now get this as the backtrace ``` Backtrace: 0: panic::frame2...

> I've tried to add some documentation for this in #407 awesome, I was thinking we might also want to add a note about `force-unwind-tables` to various pages of panic...

I'd like to implement this feature