commit | 51b0ea033ea7fd6cab2441b61d58776738c3c6c1 | [log] [tgz] |
---|---|---|
author | Claudio DeSouza <cdesouza@chromium.org> | Mon Jul 21 17:45:38 2025 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 21 17:48:31 2025 |
tree | 427b723c7731d3d9adf6c33eb3e744d741a228ba | |
parent | 1f61989abe1df43ddefc96f4ca65c41c75eb85e4 [diff] |
[exit-time-destructors] Exclude target with warnings This CL is part of number of CLs disabling `-Wexit-time-destructors`in places where this warning is going off. This will allow having this warning enabled-by-default across the codebase, whilst documenting the places where corrections for this warning are necessary. This change exclude targets under: - testing/libfuzzer This CL was uploaded by an experimental version of git cl split Bug: 40031409, 430332953 Change-Id: I949ddd4524906155fa668319aebae229e6ec78b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6759263 Auto-Submit: Claudio DeSouza <cdesouza@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Reviewed-by: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1489639} NOKEYCHECK=True GitOrigin-RevId: d35c68da4c751a8c0473c116d3a6e345561dff9a
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.