You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During fuzzing I found that the following module was consider invalid by wabt due to a leb128 parsing error. Binaryen choose to "reject" this module but precise that it is a valid module. Other tools like wasmer, wasmtime and wasm-tools valid this module.
This is an "error" because the custom dynlink section is malformed. wasm-validate currently fails in this case, but will just produce only a warning if run with --ignore-custom-section-errors. Perhaps this is the wrong default? @sbc100 wdyt?
Hi,
During fuzzing I found that the following module was consider invalid by wabt due to a
leb128
parsing error. Binaryen choose to "reject" this module but precise that it is a valid module. Other tools like wasmer, wasmtime and wasm-tools valid this module.Reproducing
Download:
reject_leb128_wabt.zip
WABT:
$ ./wasm-validate reject_leb128_wabt.wasm 0000016: error: unable to read u32 leb128: table_size
Other tools:
Branch: master
commit: 15264cd
The text was updated successfully, but these errors were encountered: