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
BiLock assertion failure and segfault in --release mode (single-threaded!) #296
Comments
Minimized to not use mio-uds or tokio-core, still working on it. |
Looks like this may be a compiler bug :( |
Thanks for looking into this. In rust-lang/rust#38437 you seem to be suggesting that the problem only exists on nightly. Note, however, that the program that I pasted in my original comment above also behaves weirdly on stable and beta. |
Yeah that's why I want to leave this open. I think that they're all related to the same bug, and my guess is that codegen changed between stable/beta/nightly to hide the bug of the reduced test case on stable/beta but leave it exposed on nightly. Put another way, my hope (and assumption) is that fixing rust-lang/rust#38437 will fix this test case on all three channels. If that isn't the case though I'll keep digging into the stable/beta versions. |
Ok I just confirmed that rust-lang/rust#38600 fixed this, so closing now that it's landed. |
Consider the following program (which has been minimized from a much more complex situation):
If I run it in debug mode, it exits without error, as I would expect. If I run in in release mode, I see, to my surprise:
The assertion being tripped is in
BiLock::drop()
The text was updated successfully, but these errors were encountered: