| commit | 00c72cfca8cfa6a8afc058ddf49238a17f864d05 | [log] [tgz] |
|---|---|---|
| author | Antonio Alphonse <alphonsea@google.com> | Fri Dec 12 09:13:38 2025 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Dec 12 09:21:43 2025 |
| tree | e76f6b82330271d75203bfe19548094109f79e93 | |
| parent | f1e12a1b5cea1a2aa59192de48e492cfb7b3b6d6 [diff] |
[Fuzzing] Add test for check failure stacktraces. Bug: 40948553 Change-Id: If5672f7b9baf4cc76919fce89f3f27a59cc6c289 Cq-Include-Trybots: luci.chromium.try:chromeos-x64-libfuzzer-asan-rel-tests,linux-x64-centipede-asan-rel-tests,linux-x64-libfuzzer-asan-dbg-tests,linux-x64-libfuzzer-asan-rel-tests,linux-x64-libfuzzer-msan-rel-tests,linux-x64-libfuzzer-ubsan-rel-tests,linux-x86-libfuzzer-asan-rel-tests,mac-arm64-libfuzzer-asan-rel-tests,win-x64-libfuzzer-asan-rel-tests Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5904310 Commit-Queue: Titouan Rigoudy <titouan@chromium.org> Reviewed-by: Titouan Rigoudy <titouan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1557915} NOKEYCHECK=True GitOrigin-RevId: 0328bbebd7b52a70c15cca551bd7f1904818d1f3
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.