-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Rust 1.67.0 breaks unit tests #26
Comments
This fixes an issue with Rust 1.67.0, possibly related to changes to the layout of types without a specified representation. trussed-dev#26
This fixes an issue with Rust 1.67.0, possibly related to changes to the layout of types without a specified representation. trussed-dev#26
This fixes an issue with Rust 1.67.0, possibly related to changes to the layout of types without a specified representation. trussed-dev#26
This fixes an issue with Rust 1.67.0, possibly related to changes to the layout of types without a specified representation. #26
This fixes an issue with Rust 1.67.0 and littlefs2, see: trussed-dev/littlefs2#26
This fixes an issue with Rust 1.67.0 and littlefs2, see: trussed-dev/littlefs2#26
This fixes an issue with Rust 1.67.0 and littlefs2, see: trussed-dev/littlefs2#26
This fixes an issue with Rust 1.67.0 and littlefs2, see: trussed-dev/littlefs2#26
Very odd. Here's a somewhat minimal failing test:
Both |
@sosthene-nitrokey suggested that this may be caused by a struct with an undefined representation being used in the FFI causing undefined behavior as this is known to break stuff with 1.67.0. https://octodon.social/@rust/109759251309886588 But as far as I see, all relevant structs already have |
I think I found the issue. It looks like this is just the lookahead buffer issue in disguise – the buffer overflow just manifests differently with 1.67.0. Fixed by #24. |
As we fixed the lookahead buffer overflow, we can now use the latest stable Rust again. Fixes trussed-dev#26 Fixes trussed-dev#28
Can also manifest as a segfault (e. g. if compiled with
|
Oh, so it's our bug, and not a compiler regression? |
Yes, I think so. The layout changes in Rust 1.67.0 probably just cause us to access a different memory region causing a different error. |
As we fixed the lookahead buffer overflow, we no longer have to pin the Rust version. Fixes trussed-dev#26 Fixes trussed-dev#28
As we fixed the lookahead buffer overflow, we no longer have to pin the Rust version. Fixes trussed-dev#26 Fixes trussed-dev#28
The text was updated successfully, but these errors were encountered: