Skip to content

reference to packed field is unaligned #19

Open

Description

@CheetoTrump

Ive tried
ntapi = "0.4.1"
ntapi = "0.4.0"
ntapi = "0.3.7"

and 32bit and 64bit for each version

I get these errors when compiling the crate

error[E0793]: reference to packed field is unaligned
--> C:\Users\USER.cargo\registry\src\index.crates.io-6f17d22bba15001f\ntapi-0.3.7\src\ntexapi.rs:2783:52
|
2783 | *tick_count.QuadPart_mut() = read_volatile(&(*USER_SHARED_DATA).u.TickCountQuad);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: packed structs are only aligned by one byte, and many modern architectures penalize unaligned field accesses
= note: creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)
= help: copy the field contents to a local variable, or replace the reference with a raw pointer and use read_unaligned/write_unaligned (loads and stores via *p must be properly aligned even when using raw pointers)

error[E0793]: reference to packed field is unaligned
--> C:\Users\USER.cargo\registry\src\index.crates.io-6f17d22bba15001f\ntapi-0.3.7\src\ntexapi.rs:2807:25
|
2807 | ((read_volatile(&(*USER_SHARED_DATA).u.TickCountQuad).wrapping_mul((*USER_SHARED_DATA).TickCountMultiplier as u64)) >> 24) as u32
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: packed structs are only aligned by one byte, and many modern architectures penalize unaligned field accesses
= note: creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)
= help: copy the field contents to a local variable, or replace the reference with a raw pointer and use read_unaligned/write_unaligned (loads and stores via *p must be properly aligned even when using raw pointers)

For more information about this error, try rustc --explain E0793.
error: could not compile ntapi (lib) due to 2 previous errors

Activity

  1. eminence commented on Jun 16, 2023

    @eminence

    This was fixed in the 0.4 release. From the paths in the logs above, you're still using ntapi-0.3.7

  2. bleak-and-bare commented on Jun 22, 2023

    @bleak-and-bare

    I don't quite get it, why is Cargo/the compiler still using version 0.3.7 of the lib even if one has set explicitly
    ntapi = "0.4" in Cargo.toml

  3. eminence commented on Jun 22, 2023

    @eminence

    You probably have some other dependency that is requiring 0.3.7 (so both 0.3.7 and 0.4.x are brought into your crate graph).

    Try running cargo tree -i ntapi to see all the packages that depend on ntapi

  4. CheetoTrump commented on Jul 2, 2023

    @CheetoTrump
    Author

    i should have sent all 3 errors but i didnt, they were 1:1 but different versions of ntapi

  5. Gordon01 commented on Sep 2, 2023

    @Gordon01

    cargo update may help in such cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions