20331dea3f
No-Try: true Docs-Preview: https://skia.org/?cl=125241 Bug: skia: Change-Id: I5bf3409a0a7895e636a9b0c6845239bb17b42fa5 Reviewed-on: https://skia-review.googlesource.com/125241 Reviewed-by: Joe Gregorio <jcgregorio@google.com> Reviewed-by: Mike Klein <mtklein@google.com> Commit-Queue: Joe Gregorio <jcgregorio@google.com> Commit-Queue: Mike Klein <mtklein@google.com> Auto-Submit: Kevin Lubick <kjlubick@google.com>
21 lines
852 B
Markdown
21 lines
852 B
Markdown
Reproducing Skia Fuzzes
|
|
=======================
|
|
|
|
We assume that you can [build Skia](/user/build). Many fuzzes only reproduce
|
|
when building with ASAN or MSAN; see [those instructions for more details](./xsan).
|
|
|
|
All that is needed to reproduce a fuzz downloaded from ClusterFuzz, oss-fuzz or
|
|
fuzzer.skia.org is to run something like:
|
|
|
|
out/ASAN/fuzz -b /path/to/downloaded/testcase
|
|
|
|
The fuzz binary will try its best to guess what the type/name should be based on
|
|
the name of the testcase. Manually providing type and name is also supported, like:
|
|
|
|
out/ASAN/fuzz -t filter_fuzz -b /path/to/downloaded/testcase
|
|
out/ASAN/fuzz -t api -n RasterN32Canvas -b /path/to/downloaded/testcase
|
|
|
|
To enumerate all supported types and names, run the following:
|
|
|
|
out/ASAN/fuzz --help # will list all types
|
|
out/ASAN/fuzz -t api # will list all names |