| commit | f8618d96757aef58e54c26cd5b4ab242cd89ac18 | [log] [tgz] |
|---|---|---|
| author | Michael Crouse <mcrouse@chromium.org> | Mon Dec 14 23:29:31 2020 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 14 23:35:40 2020 |
| tree | 334c58f4f1c619dc8943fbcbc6d36ec22df64172 | |
| parent | 0cba40d03b30fc5cef0cd612a8e0b52e6ff131a3 [diff] |
[LanguageDetection] Rename model elements of LanguageDetectionDetails. This is a global replace of: /cld_language/model_detected_language /is_cld_reliable/is_model_reliable Bug: 1157983 Change-Id: I9471600db6ae3221dd63fa92ee30d8c093748b20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587620 Auto-Submit: Michael Crouse <mcrouse@chromium.org> Reviewed-by: Donn Denman <donnd@chromium.org> Reviewed-by: Jonathan Metzman <metzman@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Trevor Perrier <perrier@chromium.org> Reviewed-by: Scott Little <sclittle@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#836839} GitOrigin-RevId: 0ebf0d592f864e372cf01f75d9477a6a693a8cac
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.