From 2031ab5c788e338954d7b37da13039eff0a7c354 Mon Sep 17 00:00:00 2001 From: Jeremy Leconte Date: Fri, 8 Nov 2024 20:30:17 +0100 Subject: [PATCH] Update fuzzer documentation. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Id9dbaf42881a3ed3f377142b116151aebfd21192 Bug: None Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/368020 Commit-Queue: Jeremy Leconte Reviewed-by: Björn Terelius Cr-Commit-Position: refs/heads/main@{#43388} --- docs/native-code/development/fuzzers/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/native-code/development/fuzzers/README.md b/docs/native-code/development/fuzzers/README.md index cac77cdc07..b323756d02 100644 --- a/docs/native-code/development/fuzzers/README.md +++ b/docs/native-code/development/fuzzers/README.md @@ -4,6 +4,12 @@ WebRTC currently uses libfuzzer for fuzz testing however FuzzTest is a new approach which we have not yet looked into but we will in the future. Before continuing, read the [libfuzzer][libfuzzer-getting-started] and [FuzzTest][fuzztest-getting-started] getting started docs to get familar. +You will also need to download libfuzzer specific libraries, which are not downloaded by default. The easiest way to do this is to set the `checkout_fuzzer` custom variable in your .gclient file then run gclient runhooks. +``` + "custom_vars": { + "checkout_fuzzer": True, + }, +``` ## Compiling locally To build the fuzzers residing in the [test/fuzzers][fuzzers] directory, use