Robbepop opened PR #5140 from rf-cleanup-wasmi-fuzzer to main:
Just some minor clean ups to the
wasmifuzzer code.
Unfortunately due to compilation/linkage problems with the OCaml based spec interpreter I could not run the fuzz tests locally so there might be bugs that I have to fix ... :/Can we run fuzz tests via CI?
Robbepop updated PR #5140 from rf-cleanup-wasmi-fuzzer to main.
alexcrichton submitted PR review.
alexcrichton created PR review comment:
Could the
.unwrap()be retained here and onmemory? If the export isn't present or is of a different type that's a bug in the fuzz harness which we need to fix and the.unwrap()helps uncoveri t.
Robbepop submitted PR review.
Robbepop created PR review comment:
yeah I just noticed that this
unwrapmight have been intentional for exactly that purpose. I will try to fix it.
Robbepop created PR review comment:
under what circumstances is
get_globalsupposed to returnSomevalue?
Robbepop submitted PR review.
Robbepop edited PR review comment.
Robbepop submitted PR review.
Robbepop created PR review comment:
Something like
self.instance .get_export(&self.store, name) .and_then(wasmi::Extern::into_global) .map(|global| global.get(&self.store)) .map(DiffValue::from) .unwrap() .into() ``` Or would you rather have the original code back? ~~~
Robbepop updated PR #5140 from rf-cleanup-wasmi-fuzzer to main.
alexcrichton submitted PR review.
alexcrichton created PR review comment:
This is intended for JS where JS can't get the value of an exported
v128global, for example. So only for situations where the engine for some reason is unable to retrieve the value. Forwasmithough it should be able to retrieve the value in all situations.
Robbepop has marked PR #5140 as ready for review.
Last updated: Dec 06 2025 at 06:05 UTC