-
Notifications
You must be signed in to change notification settings - Fork 674
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
Can't zero-initialize SockType #1212
Comments
Please tell us your operating system, kernel version, and Rust toolchain version. And paste the complete error message. |
OS: Debian GNU/Linux 10 (buster) Error message from
|
This is a new error introduced by the latest nightly compiler. It really should just be a warning so as not to break existing code. But I'm already working on a fix. |
Also, if this remains an error by the time that 1.44.0 goes stable, then we'll need to backport the fix to all currently used Nix releases. |
1214: Fix UB in getsockopt r=asomers a=asomers The old code tried to zero-initialize an enum for which 0 is not a valid value. That worked for older compilers, but triggers a panic with Rust 1.44.0. The correct technique is to use mem::MaybeUninit. Fixes #1212 Co-authored-by: Alan Somers <[email protected]>
Hi Team,
I have observed the following two tests to fail on my machine:
Please let me know how I can help troubleshoot them.
The text was updated successfully, but these errors were encountered: