| commit | c561b4dbad651c63e63a6f7015605ef67743c360 | [log] [tgz] |
|---|---|---|
| author | Florin Malita <[email protected]> | Mon Nov 03 17:29:05 2025 |
| committer | Copybara-Service <[email protected]> | Mon Nov 03 17:32:21 2025 |
| tree | 816bfbc622289b7d167c8b05c0936298bf074a58 | |
| parent | 7446275606dd9230e854b898d9c6a5e76bd42729 [diff] |
[pathbuilder] Enforce immutable SkPath APIs globally Path-editing methods in Skia's SkPath are being deprecated. This is the final step in migrating Chromium to SkPathBuilder. Turn on SK_HIDE_PATH_EDIT_METHODS to enforce non-editing SkPath APIs. Refactor remaining call sites (that were missed in previous cleanup CLs) to use SkPathBuilder or named factories. No functional changes. Bug: 378688986 Change-Id: Ib088b78a7ac798fe83004252694d7c3a867531f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7101838 Reviewed-by: Mike Reed <[email protected]> Reviewed-by: Ali Hijazi <[email protected]> Reviewed-by: Dana Fried <[email protected]> Reviewed-by: Toni Barzic <[email protected]> Reviewed-by: Mitsuru Oshima <[email protected]> Reviewed-by: Thomas Anderson <[email protected]> Reviewed-by: Ted Choc <[email protected]> Commit-Queue: Florin Malita <[email protected]> Cr-Commit-Position: refs/heads/main@{#1539408} NOKEYCHECK=True GitOrigin-RevId: 63267f2f424009cfa9a3f5e05877b9c2a0647ede
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.