Lines Matching refs:fuzzing

11 LibFuzzer is in-process, coverage-guided, evolutionary fuzzing engine.
14 library via a specific fuzzing entrypoint (aka "target function"); the fuzzer
56 and so it is possible and even desirable to use it with other fuzzing engines
61 * The fuzzing engine will execute the fuzz target many times with different inputs in the same proc…
65 …Non-determinism (e.g. random decisions not based on the input bytes) will make fuzzing inefficient.
117 fuzzing entrypoint still works and that all of the sample inputs run through
120 If you have a large corpus (either generated by fuzzing or acquired by other means)
157 By default, the fuzzing process will continue indefinitely – at least until
159 stopping the fuzzing process, and the particular input that triggered the bug
174 that `N` fuzzing jobs should be run to completion (i.e. until a bug is found or
222 then it will re-run those files as test inputs but will not perform any fuzzing.
272   by other fuzzing processes.
274   Number of fuzzing jobs to run to completion. Default value is 0, which runs a
275   single fuzzing process until completion.  If the value is >= 1, then this
276   number of jobs performing fuzzing are run, in a collection of parallel
280   Number of simultaneous worker processes to run the fuzzing jobs to completion
295   Provide a prefix to use when saving fuzzing artifacts (crash, timeout, or
308   try to detect memory leaks during fuzzing (i.e. not only at shut down).
481 the fuzzing but is very likely to improve the results.
505 Sometimes the code under test is not fuzzing-friendly. Examples:
515 In many cases it makes sense to build a special fuzzing-friendly build
516 with certain fuzzing-unfriendly features disabled. We propose to use a common build macro
523     // In fuzzing mode the behavior of the code should be deterministic.
544 Currently, there is no simple way to run both fuzzing engines in parallel while sharing the same co…
598 For in-process fuzzing this is inconvenient
657   asserts/crashes on invalid inputs, in-process fuzzing is not applicable.
672   execution of one test) the fuzzing results will be unreliable.