Lines Matching full:your

5 maximize your results.
8 **Note:** If you haven’t created your first fuzz target yet, see the [Getting
12 The most direct way to gauge the effectiveness of your fuzz target is to collect
14 page after your fuzz target is checked into the Chromium repository.
33 You should aim for at least 1,000 exec/s from your fuzz target locally before
42 If your `LLVMFuzzerTestOneInput` function is too complex, it can decrease the
63 **Note:** It’s always a good idea to try different variants for your fuzz target
69 You can check the percentage of code covered by your fuzz target to gauge
75 * Generate a source-level coverage report for your fuzzer by running the
107 are checksums and magic numbers. Or, it may be impossible for your fuzzer to
121 You can give your fuzz target a starting point by creating a set of valid and
131 * For file format parsers, add valid files from your test suite.
150 in the Chromium source repository. You can define one in your `BUILD.gn` file by
151 adding a `seed_corpus` attribute to your `fuzzer_test` target definition:
177 If you can't store your seed corpus in the Chromium repository (e.g., it’s too
181 1) Open the [Corpus GCS Bucket] in your browser.
184 3) In the `<my_fuzzer>` directory, upload your corpus files.
187 **Note:** If you upload your corpus to GCS, you don’t need to add the
188 `seed_corpus` attribute to your `fuzzer_test` target definition. However, adding
199 **Note:** To write to this bucket using `gsutil`, you must be logged into your
201 login` command to log into your account in `gsutil` if you installed `gsutil`
207 Your seed corpus is synced to all fuzzing bots for every iteration, so it's
212 You can minimize your seed corpus by using libFuzzer’s `-merge=1` option:
223 minimized corpus that gives the same code coverage as your initial `seed_corpus`
228 You can help your fuzzer increase its coverage by providing a set of common
259 2) Test your dictionary by running your fuzz target locally:
268 3) Add the dictionary file in the same directory as your fuzz target, then add
269    the `dict` attribute to the `fuzzer_test` definition in your `BUILD.gn` file:
283 If you need to change the code being tested by your fuzz target, you can use an
284 `#ifdef FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION` macro in your target code.