[COIL] Change chromium code search type links to use main rather than master for testing

    See this doc: go/chromium-coil-change for more info
    BUG=1210385

Change-Id: I646cf6ac1125b021b2dd84cdf2fee30958fd8a92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902983
Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: John Palmer <jopalmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#884847}
NOKEYCHECK=True
GitOrigin-RevId: a8515fcac91e2342b2afe2b3a7046acceec2e59a
1 file changed
tree: df352b4fcba8610d19a27a2578794fd8a88c4111
  1. AFL_integration.md
  2. BUILD.gn
  3. OWNERS
  4. README.md
  5. archive_corpus.py
  6. dictionary_generator.py
  7. efficient_fuzzing.md
  8. fuzzer_test.gni
  9. fuzzers/
  10. gen_fuzzer_config.py
  11. gen_fuzzer_owners.py
  12. getting_started.md
  13. libFuzzer_integration.md
  14. libfuzzer_exports.h
  15. libprotobuf-mutator.md
  16. proto/
  17. reference.md
  18. reproducing.md
  19. tests/
  20. unittest_main.cc
  21. zip_sources.py
README.md

Fuzz testing in Chromium

go/chrome-fuzzing

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.

Getting Started

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.

Advanced Topics

Further Reading

Trophies

Other Links