commit | 1ff77e987e2ac9ea1abde097d951b3fab7f2a3b6 | [log] [tgz] |
---|---|---|
author | Mike Reed <reed@google.com> | Thu May 28 22:08:50 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu May 28 22:08:50 2020 |
tree | ce7c0bb8fd83b090724978c82208629aaa5c628c | |
parent | 177369ab0b127ca83f344ca2916f73b37d941496 [diff] |
Remove references to deprecated, unused SkPaint::kStrokeAndFill Bug: skia:8428 Change-Id: I14df4bc8d64f7d020c733c8460bdc7474e1b7d2d TBR: kcc@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2213335 Commit-Queue: Mike Reed <reed@google.com> Reviewed-by: Florin Malita <fmalita@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#772906} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 82a171126adfe8f4d07314ab014f531242f7a4d6
Fuzzing is a testing technique that feeds auto-generated inputs to a piece of target code in an attempt to crash the code. It's one of the most effective methods we have for finding security and stability issues (see go/fuzzing-success). You can learn more about the benefits of fuzzing at go/why-fuzz.
This documentation covers the in-process guided fuzzing approach employed by different fuzzing engines, such as libFuzzer or AFL. To learn more about out-of-process fuzzers, please refer to the Blackbox fuzzing page in the ClusterFuzz documentation.
In Chromium, you can easily create and submit fuzz targets. The targets are automatically discovered by buildbots, built with different fuzzing engines, then uploaded to the distributed ClusterFuzz fuzzing system to run at scale.
Create your first fuzz target and submit it by stepping through our Getting Started Guide.
Creating a fuzz target that expects a protobuf instead of a byte stream as input.
Reproducing bugs found by libFuzzer/AFL and reported by ClusterFuzz.