-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust generates bad debug info for panics #44465
Comments
So #46101 made me get into this, and
|
So this is actually an LLVM bug that was apparently fixed in llvm-mirror/llvm@5c08882 - BranchFolding had used to nuke debug info, now it doesn't - which is a commit contained in LLVM 5.0. So this should be fixed when we upgrade to that. That commit is somewhat big, so I'm not sure how safe it is to apply to 4.0. |
Thank you so much for investigating, @arielb1! |
Did the upgrade to LLVM 5.0 happen? Did this bug get fixed? |
@steven-michaud Rust's currently on LLVM 9.0 |
Thanks for the info. So this bug should have been fixed. Does anyone know if it was? |
visiting for wg-debugging triage closing; presumed fixed. please reopen if you have evidence that this is still a problem |
We're getting crashes in webrender that look like this:
8 XUL webrender::frame_builder::{{impl}}::build src/libcore/option.rs:0
However webrender::frame_builder::{{impl}}::build is not found at option.rs:0
In https://bugzilla.mozilla.org/show_bug.cgi?id=1398171 @luser elaborates the problem with debug info that rust is generating.
The text was updated successfully, but these errors were encountered: