Skip to content
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

Different output when running a same binary #2858

Closed
abc767234318 opened this issue Dec 4, 2023 · 2 comments
Closed

Different output when running a same binary #2858

abc767234318 opened this issue Dec 4, 2023 · 2 comments

Comments

@abc767234318
Copy link

I used the interpreter mode of different runtimes to run randomly generated wasm binaries, and the output from wamr is different from the other runtimes.
3605.zip

iwasm --heap-size=0 -f 4 3605.wasm 1
-----------------wamr-----------------
WASM module load failed: type mismatch: br_table targets must all use same result type

-----------------wasmedge-----------------
[2023-11-22 22:19:18.333] [error] execution failed: out of bounds memory access, Code: 0x88
[2023-11-22 22:19:18.333] [error]     Accessing offset from: 0xb1a6c5f6 to: 0xb1a6c5f7 , Out of boundary: 0x000fffff
[2023-11-22 22:19:18.333] [error]     In instruction: i64.load16_s (0x32) , Bytecode offset: 0x00000f7e
[2023-11-22 22:19:18.333] [error]     When executing function name: "4"

@wenyongh
Copy link
Contributor

wenyongh commented Dec 5, 2023

@abc767234318 Thanks for spotting the issue! Please try #2864.

@wenyongh
Copy link
Contributor

wenyongh commented Jan 5, 2024

Close this issue as it was fixed.

@wenyongh wenyongh closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants