-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Segfault in futex_wait() on riscv64gc-unknown-linux-gnu with rustc 1.64.0 #102866
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
The dmesg info may be useful:
|
Aha, it's a regression. Doesn't happen with 1.58.0. I'll track it down to the exact version. |
You might want to use https://github.com/rust-lang/cargo-bisect-rustc |
Oh, that's not the right backtrace. I think gdb just halts on any signal, and that's a SIGUSR1 not a SIGSEGV. Everything is fine when the program is there. Perhaps this is helpful: https://peeterjoot.wordpress.com/2010/07/07/avoiding-gdb-signal-noise/ (I usually debug from core dumps, which is one way around this) |
Thanks Saethlin, yes, I should have known better than that. This looks more likely:
Note the fault was introduced post 1.63.0 and it doesn't reproduce on rust version 1.66.0-nightly (81f3919 2022-10-09), so we can probably close this (I wanted to capture the bug right away in case I didn't get time to dig deeper). I'll leave it for open in case somebody want me to run another experiment. |
Ok, clearly a dup of #102155 |
Uh oh!
There was an error while loading. Please reload this page.
Note, this does not appear to be related to issue #102155 but I can't be sure.
I'm many levels deep in the original problem, but traced it down to autocfg not building (filed here: cuviper/autocfg#51); the repro is trivial.
The back trace however makes me suspect this is a deeper issue:
Unfortunately I don't have the expertise to debug this.
The text was updated successfully, but these errors were encountered: