-
Notifications
You must be signed in to change notification settings - Fork 51
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
Panics on Rust 1.78: "unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceed isize::MAX
"
#106
Comments
Same here on latest Rust nightly ( Backtrace
|
Precondition assertions are only enabled by default on debug builds |
Anyone having a case and more details to consistently reproduce? |
I delete cargo.lock and generate a new one, it fixed. Now I can debug my rust program.
It will compile schannel v0.1.20 before and produce the panic, now it will compile schannel v0.1.23 and will not produce the panic, I hope this information could help. |
Unfortunately we're using 0.1.23 and still see the panic (this is my lockfile) |
Had the same problem with 0.1.19 on windows 10 and rust 1.79.0, upgrading to 0.1.23 solved it for me - fix commit |
Any occurences in recent rust versions and 0.1.24? |
I encountered this panic making a request using reqwest with the Tokio runtime. This seems to be an UB caughted by the new precondition assertions.
Here's the backtrace:
The text was updated successfully, but these errors were encountered: