| commit | 79b625ff1c4c4cffd845986ef5b186af310f3e71 | [log] [tgz] |
|---|---|---|
| author | Arthur Eubanks <aeubanks@google.com> | Mon Apr 12 18:35:04 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 12 18:41:25 2021 |
| tree | fa5619dfe834facf7f1a2ed0c6bc0913a01f700c | |
| parent | ee82808f42e3b411dca2e85959a9f2c6e8dc0f71 [diff] |
Revert "Use a build flag to turn off LITE mode" This reverts commit a8fe7b364da3a44cafb9bde3202036c01d5b8444. Reason for revert: Breaks many ASan/libfuzzer bots: https://crbug.com/1198031 Original change's description: > Use a build flag to turn off LITE mode > > We don't need a protoc plugin anymore. There are now generator options to > configure the optimize_for value. > https://github.com/protocolbuffers/protobuf/issues/487 > > Change-Id: I587cc4f720705f8d8f8393555127df25ae797525 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2817620 > Commit-Queue: David Benjamin <davidben@chromium.org> > Auto-Submit: David Benjamin <davidben@chromium.org> > Reviewed-by: Jonathan Metzman <metzman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#871126} Change-Id: I31d6013b6a47ef7892a20dd6ac66e7d1486186e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2818427 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Jonathan Metzman <metzman@chromium.org> Commit-Queue: Arthur Eubanks <aeubanks@google.com> Cr-Commit-Position: refs/heads/master@{#871559} GitOrigin-RevId: d8c386ec6864164e104977a9a72f4142b3b6fa8a
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.
Fuzzing mojo interfaces using automatically generated libprotobuf-mutator fuzzers.