-
Notifications
You must be signed in to change notification settings - Fork 13.4k
RUST_BACKTRACE truncated with -Cpanic=abort #81902
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This happens because See rust-lang/backtrace-rs#397 for more information. |
Maybe we should find a way to remove the |
How would that work? Plain checking for |
Thinking a bit more about this, I think linking the creation of unwind tables to the panic method is not a sensible thing. |
I second this, I started using Having to add Is it still possible to change the behavior of I also think the behavior and the solution should be documented here. |
When using
-Cpanic=abort
, the resulting panic backtrace is being truncated.Interestingly, when wrapping with a custom panic hook, this problem is even worse.
Tested on nightly and stable. Only seems to be a problem on mac and linux, windows does not seem to be effected.
RUST_BACKTRACE=full with -Cpanic=unwind
RUST_BACKTRACE=full with -Cpanic=abort
Using only
RUST_BACKTRACE=1
in that case will not print any backtrace at all.The text was updated successfully, but these errors were encountered: