-
Notifications
You must be signed in to change notification settings - Fork 252
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
gimli: Enable backtrace for FreeBSD #402
Conversation
It is just @lzutao's earlier PR, rebased over the uclibc merge conflict. |
Thanks! Is this ready to land with libc changes published? |
Edit: dl_iterate_phdr was merged Oct 27; libc 0.2.81 was published Dec 6. That contains the dl_iterate_phdr addition: https://github.com/rust-lang/libc/releases/tag/0.2.81 => 70962e3943d22d94141954db18eb7295b5edec5d So I think we're good! |
To confirm, have you tested this on the platforms enabled here? If so I think the |
I have not. I can test on FreeBSD but I don’t have any of the other systems. Would that just be |
Yes a |
277e2d9
to
eca94be
Compare
Ok, that was fast. I think I must have already run it. It passes. However, I think the tests may need platform adjustment as well to actually cover this change. Give me a few minutes... Edit: well, I don't know how to tell if we are actually testing gimli-symbolize-ation on FreeBSD.
They're tier 2+ platforms, right? I'm worried we might be applying higher scrutiny to restoring functionality that was lost in rust 1.47 than we were in losing it in the first place. At the same time, I don't feel strongly about Open/NetBSD support and am ok dropping them if you insist. |
My main goal is that if you're explicitly affecting new targets in this PR there should at least be confidence that the code compiles. It doesn't sound like you're checking that for all the platforms listed here? I would ideally like confirmation that the tests work with this PR. If there are other bugs then they should be filed as new issues. |
Ok, I’ll drop the non-FreeBSD diff. Cargo test passes. |
eca94be
to
4c7f391
Compare
Thanks! |
Thank you! :-) |
#384 attempt number 2.
Closes #325.