AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
a58bbd5ebc
v8/test/fuzzer/wasm_async
History
Andreas Haas 7b53a0e010 [wasm] Avoid executing infinite loops in the wasm fuzzers 
The wasm-async fuzzer uses the bytes provided by the fuzzer engine
directly as wasm module bytes, compiles them with async compilation, and
then tries to execute the "main" function of the module. This "main"
can have an infinite loop which causes a timeout in the fuzzer. With
this CL the "main" function is first executed with the interpreter. If
the execution in the interpreter finishes within 16k steps, which means
that there is no infinite loop, also the compiled code is executed.

I added the raw fuzzer input as a test case because in this case I
really want to test the fuzzer and not V8.

R=clemensh@chromium.org

Bug: chromium:761784
Change-Id: Id1fe5da0da8670ec821ab9979fdb9454dbde1162
Reviewed-on: https://chromium-review.googlesource.com/651046
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#47874}
2017-09-07 12:35:45 +00:00
..
README.md [wasm] Add a fuzzer for async compilation 2017-06-13 15:13:06 +00:00
regression-761784.wasm [wasm] Avoid executing infinite loops in the wasm fuzzers 2017-09-07 12:35:45 +00:00
valid.wasm [wasm] Move ScheduledErrorThrower to wasm-api.h 2017-08-03 08:45:58 +00:00

README.md

All files in this directory are used by the trybots to check that the fuzzer executes correctly, see https://github.com/v8/v8/blob/master/test/fuzzer/README.md. There should be at least one file in this directory, e.g. this README file.