Lines Matching refs:fuzzer

3 randomly, focusing on specific APIs). For example, we have a codec fuzzer which takes a mutated
4 png/jpeg or similar file and attempts to turn it into an `SkImage`. We also have a canvas fuzzer
9 that contains all fuzzers and is a convenient way to reproduce fuzzer-reported bugs. There are also
10 single fuzzer executables containing exactly one fuzzer, which are convenient to build with
28 When enabling a fuzzer in OSS-Fuzz, we typically need to follow these steps:
29   1. *Add a seed corpus to `gs://skia-fuzzer/oss-fuzz/` (in the
30 …[skia-public project](https://console.cloud.google.com/storage/browser/skia-fuzzer?project=skia-pu…
37      to build the desired fuzzer target and move it into $OUT. If there is a seed corpus, move
38      it into $OUT and make sure it is the same name as the fuzzer executable with `_seed_corpus.zip`
53 <https://oss-fuzz.com/fuzzer-stats> is useful to see metrics on how our fuzzers are running. It
54 shows things like executions per second (higher is better), edge coverage percent per fuzzer,
59 … by libFuzzer](https://oss-fuzz.com/fuzzer-stats?group_by=by-fuzzer&date_start=2021-08-16&date_end…
60 …ven by afl-fuzz](https://oss-fuzz.com/fuzzer-stats?group_by=by-day&date_start=2021-08-16&date_end=…
62 That dashboard also has a Coverage Report. Even though it appears the Coverage report is per fuzzer,
67 …- [Creating a binary fuzzer](https://docs.google.com/document/d/1QDX0o8yDdmhbjoudNsXc66iuRXRF5XNNq…
68 …- [Creating an API fuzzer](https://docs.google.com/document/d/1e3ikXO7SwoBsbsi1MF06vydXRlXvYalVORa…