-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
All stacktrace lines are "<unknown>" on FreeBSD #78184
Comments
Can you test on old Rust stable version to see if this is a regression ? Edit: This is an expected regression rust-lang/backtrace-rs#325. |
It worked on 1.46.0:
|
This comment has been minimized.
This comment has been minimized.
Assigning |
For what it's worth, this problem occurs on iOS (x86_64-apple-ios) builds too: 1.47.0:
1.46.0:
|
Likely caused by #74682. (switching from libbacktrace to gimli) It seems that |
For iOS it may or may not work to extend the condition at https://github.com/rust-lang/backtrace-rs/blob/8eee2e473e71e659cbd5d32ee78aaf42e8b75752/src/symbolize/gimli.rs#L204 to include iOS too. |
You're right! I submitted a PR to fix it for iOS. Thanks a lot! |
@cutsoy You might want to file another PR to update backtrace-rs submodule in this repo. |
It looks like dl_iterate_phdr exists on FreeBSD, so I think we could just extend https://github.com/rust-lang/backtrace-rs/blob/8eee2e473e71e659cbd5d32ee78aaf42e8b75752/src/symbolize/gimli.rs#L353-L356 to cover FreeBSD |
Looks good!
|
backtrace-rs issue: rust-lang/backtrace-rs#325 backtrace-rs PR for issue: rust-lang/backtrace-rs#402 |
What's left to do here? Would a PR that updates the submodule for library/backtrace be sufficient? |
…lacrum Update backtrace to 0.3.56 Fixes rust-lang#78184
When panicking, every line of stack traces contain
<unknown>
instead of a code location. E.g.I'm on rustc 1.47.0 and FreeBSD 12.1:
Possible duplicate of #54434
I've tried mounting /proc but it didn't fix the problem.
The text was updated successfully, but these errors were encountered: