-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[crash] assertion failed or unimplemented panic when table type is not anyref #1601
Comments
Thanks for the report! There are known issues in the implementations of some wasm proposals right now, and for example reference types are known to not be fully implemented (same with SIMD and threads). Our own fuzzing has a whitelist of which wasm proposals that we fuzz against, and it's specifically not enabling all of them. This is perhaps something that would be good to update the documentation for though to indicate that some wasm proposals exported from |
Hi Alex, Oh interesting, effectively I checked the documentation for the different In a more generic way, i'm not a big fan of macros in Rust that can lead to panics so I always prefer to report them even if project is under development. I let you decided when to close this issue ;) |
Be sure to warn users that the entirety of some proposals are not implemented, so bugs should be expected. Closes bytecodealliance#1601
Be sure to warn users that the entirety of some proposals are not implemented, so bugs should be expected. Closes #1601
Description
Hey guys,
During fuzzing
wasmtime
withcranelift
backend and almostall features enabled
in the config, I trigger those bugs:If you process the crashing wasm module using
wasmtime = "0.15"
crate, you will trigger a reachable assertion (CWE-617):If you process the wasm module using wasmtime cli, you will trigger an unimplemented panic:
Steps to reproduce the issue
Download the crashing file: assert_wasmtime_table_type_anyref.zip
Testing piece of code:
Which Wasmtime version / commit hash / branch are you using?
crate version:
wasmtime = "0.15.0"
Wasmtime cli version:
wasmtime 0.15.0
The text was updated successfully, but these errors were encountered: