Stream: git-wasmtime

Topic: wasmtime / issue #7624 aarch64: `WasmFault` calculated wi...

Wasmtime GitHub notifications bot (Dec 01 2023 at 17:58):

abrown added the bug label to Issue #7624.

Wasmtime GitHub notifications bot (Dec 01 2023 at 17:58):

abrown opened issue #7624:

Test Case

See wasm_fault_address_reported_from_mpk_protected_memory in #7622

Steps to Reproduce

• Checkout the PR (e.g., gh pr checkout 7622)
• On an aarch64 machine, run `cargo test -- traps::wasm_fault_address_reported_from_mpk_protected_memory

Expected Results

The test to pass.

Actual Results

The test fails because the error message contains 0xdeadbee8 instead of the expected 0xdeadbeef. This likely is an endianness issue causing the calculation of WasmFault (see Store::wasm_fault, e.g.) to be slightly off.

Versions and Environment

Wasmtime version or commit: TODO

Operating system: TODO

Architecture: TODO

Extra Info

Anything else you'd like to add?

Wasmtime GitHub notifications bot (Dec 01 2023 at 18:00):

abrown edited issue #7624:

Test Case

See wasm_fault_address_reported_from_mpk_protected_memory in #7622

Steps to Reproduce

• Checkout the PR (e.g., gh pr checkout 7622)
• On an aarch64 machine, run `cargo test -- traps::wasm_fault_address_reported_from_mpk_protected_memory

Expected Results

The test to pass.

Actual Results

The test fails because the error message contains 0xdeadbee8 instead of the expected 0xdeadbeef. This likely is an endianness issue causing the calculation of WasmFault (see Store::wasm_fault, e.g.) to be slightly off.

Versions and Environment

Wasmtime version or commit: #7622

Operating system: Reproduced in the "Linux arm64" CI runner (here)

Architecture: aarch64

Wasmtime GitHub notifications bot (Dec 01 2023 at 18:06):

abrown edited issue #7624:

Test Case

See wasm_fault_address_reported_from_mpk_protected_memory in #7622

Steps to Reproduce

• Checkout the PR (e.g., gh pr checkout 7622)
• On an aarch64 machine, run cargo test -- traps::wasm_fault_address_reported_from_mpk_protected_memory

Expected Results

The test to pass.

Actual Results

The test fails because the error message contains 0xdeadbee8 instead of the expected 0xdeadbeef. This likely is an endianness issue causing the calculation of WasmFault (see Store::wasm_fault, e.g.) to be slightly off.

Versions and Environment

Wasmtime version or commit: #7622

Operating system: Reproduced in the "Linux arm64" CI runner (here)

Architecture: aarch64

Wasmtime GitHub notifications bot (Dec 01 2023 at 18:33):

alexcrichton closed issue #7624:

Test Case

See wasm_fault_address_reported_from_mpk_protected_memory in #7622

Steps to Reproduce

• Checkout the PR (e.g., gh pr checkout 7622)
• On an aarch64 machine, run cargo test -- traps::wasm_fault_address_reported_from_mpk_protected_memory

Expected Results

The test to pass.

Actual Results

The test fails because the error message contains 0xdeadbee8 instead of the expected 0xdeadbeef. This likely is an endianness issue causing the calculation of WasmFault (see Store::wasm_fault, e.g.) to be slightly off.

Versions and Environment

Wasmtime version or commit: #7622

Operating system: Reproduced in the "Linux arm64" CI runner (here)

Architecture: aarch64

Wasmtime GitHub notifications bot (Dec 01 2023 at 18:33):

alexcrichton commented on issue #7624:

Ah this is expected platform-specific behavior (I think we raced with my comment), so I'm going to close this.

Last updated: Dec 06 2025 at 06:05 UTC