Chromium Code Reviews| Index: testing/libfuzzer/README.md |
| diff --git a/testing/libfuzzer/README.md b/testing/libfuzzer/README.md |
| new file mode 100644 |
| index 0000000000000000000000000000000000000000..db6def38ec0797d713cda1d15b68fbe8ddb8cf74 |
| --- /dev/null |
| +++ b/testing/libfuzzer/README.md |
| @@ -0,0 +1,32 @@ |
| +# Libfuzzer in Chrome |
| + |
| +[g.co/libfuzzer-chrome] |
| + |
| +This directory contains integration between [LibFuzzer] and Chrome. |
|
mmoroz
2016/03/17 11:58:13
May be "documentation about integration" / "inform
aizatsky
2016/03/17 23:39:25
No, in this case - the directory actually contains
|
| +Libfuzzer is an in-process coverage-driven evolutionary fuzzer. It helps |
| +engineers to uncover potential stability problems earlier. |
|
mmoroz
2016/03/17 11:58:13
Let's say "security and stability"?
aizatsky
2016/03/17 23:39:25
Done.
|
| + |
| +*** note |
| +**Requirements:** libfuzzer in chrome is supported with GN on Linux only. |
| +*** |
| + |
| +## Integration Status |
| + |
| +Fuzzer tests are well-integrated with Chrome build & distributed ClusterFuzz |
|
mmoroz
2016/03/17 11:58:13
May be "Chrome build system"?
aizatsky
2016/03/17 23:39:25
Done.
|
| +fuzzing system. Cover bug: [crub.com/539572]. |
|
inferno
2016/03/17 16:49:36
typo crub->crbug
aizatsky
2016/03/17 23:39:25
Done.
|
| + |
| +## Documentation |
| + |
| +* [Getting Started Guide] walks you through all the steps necessary to create |
| +your fuzzer and submit it to ClusterFuzz. |
| +* [Efficient Fuzzer Guide] explains how to measure fuzzer effectiveness and |
| +ways to improve it. |
| +* [ClusterFuzz Integration] describes integration between ClusterFuzz and |
| +libfuzzer. |
| + |
| + |
| +[LibFuzzer]: http://llvm.org/docs/LibFuzzer.html |
| +[crub.com/539572]: https://bugs.chromium.org/p/chromium/issues/detail?id=539572 |
|
inferno
2016/03/17 16:49:36
typo crub->crbug
aizatsky
2016/03/17 23:39:25
Done.
|
| +[Getting Started Guide]: ./getting_started.md |
| +[Efficient Fuzzer Guide]: ./efficient_fuzzer.md |
| + |