Move use_fuzztest_wrapper declaration from BUILD.gn to gni file This will allow making the variable visible in other parts of the code. Bug: webrtc:42223878 Change-Id: I3ee5f882d19abe67d7a5888cc999cbdfbad04d8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6567426 Reviewed-by: Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Björn Terelius <terelius@chromium.org> Reviewed-by: Paul Semel <paulsemel@chromium.org> Cr-Commit-Position: refs/heads/main@{#1462736} NOKEYCHECK=True GitOrigin-RevId: 037e8f7f17e5c576a65b7bcf1f3bd2e13f6f9abf
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.
You should fuzz any code which absorbs inputs from untrusted sources, such as the web. If the code parses, decodes, or otherwise manipulates that input, it's an especially good idea to fuzz it.
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.