Reland "Use a build flag to turn off LITE mode"

This is a reland of a8fe7b364da3a44cafb9bde3202036c01d5b8444,
which was reverted in
https://chromium-review.googlesource.com/c/chromium/src/+/2818427. The
build failure was a result of dependency issues in
//components/cast_channel, which have since been fixed, so try this again.

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}

Bug: 1198031
Change-Id: I8919df415893b8d0ebfa8252290a7cc6600c2b4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2826403
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Jonathan Metzman <metzman@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#872920}
GitOrigin-RevId: 563a7ad064aea7e7433eec4e0a464f28f96dfa8f
1 file changed
tree: ad71fa22471887e0caeaccf8dfb128463d4383e3
  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