commit | b9591b329e926ee2735740f7a9ce8cb02ff76113 | [log] [tgz] |
---|---|---|
author | Colin Blundell <blundell@chromium.org> | Mon Jul 01 09:41:41 2024 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 01 10:02:45 2024 |
tree | 39a050017c964d9ab17391426655b82865c831bc | |
parent | b82fd710008768fff6b23e7cf59befcd55de2941 [diff] |
[Fuzzer] Restore configuration of GL impl to use stub bindings [1] removed a bunch of GL-specific configuration that was potentially no longer necessary in order to determine if there was any fallout. The fallout is [2], which indicates that it's still necessary to configure the GL implementation to use stub bindings [3]. This CL restores that configuration. [1] https://chromium-review.googlesource.com/c/chromium/src/+/5626315 [2] https://issues.chromium.org/u/1/issues/348473853#comment4 [3] https://source.chromium.org/chromium/chromium/src/+/main:ui/gl/init/gl_factory_mac.cc;l=98-100?q=gl_factory_mac.cc&ss=chromium Bug: 348473853 Change-Id: Idd75b6e7ee7290f0c5a7aeca8e670070e32e031c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5666882 Reviewed-by: Titouan Rigoudy <titouan@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1321591} NOKEYCHECK=True GitOrigin-RevId: 8893dc2d5cc8bccb14269050d304870334abe255
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.