admin/webrtc_m130
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update fuzzer documentation.

Browse Source 
Change-Id: Id9dbaf42881a3ed3f377142b116151aebfd21192
Bug: None
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/368020
Commit-Queue: Jeremy Leconte <jleconte@webrtc.org>
Reviewed-by: Björn Terelius <terelius@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#43388}
This commit is contained in:
Jeremy Leconte 2024-11-08 20:30:17 +01:00 committed by WebRTC LUCI CQ
parent a5d71009ac
commit 2031ab5c78
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/native-code/development/fuzzers/README.md
View File

@ -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. 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. 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 ## Compiling locally
To build the fuzzers residing in the [test/fuzzers][fuzzers] directory, use To build the fuzzers residing in the [test/fuzzers][fuzzers] directory, use