diff options
| author |  Kostya Serebryany <konstantin.s.serebryany@gmail.com> | 2016-12-24 20:52:24 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2016-12-24 20:52:24 -0800 |
| commit | b270737c162c92b3311d81020faac703355699cc (patch) | |
| tree | f0dd39b2974bb5a1a8ee82d862beda5efac7f8cd /docs/faq.md | |
| parent | a7a5f8ecdd7421702254d33471fe6557249bff69 (diff) | |
Update faq.md
Diffstat (limited to 'docs/faq.md')
| -rw-r--r-- | docs/faq.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/faq.md b/docs/faq.md index 1e1b7f47..0a6b1b69 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -42,6 +42,11 @@ This may or may not be considered as a real bug by the project owners, but nevertheless we treat all timeouts and OOMs as bugs since they significantly reduce the efficiency of fuzzing. +Remember that fuzzing is executed with AddressSanitizer or other +sanitizers which introduce certain ovehead in RAM and CPU. + We currently do not have a good way to deduplicate timeout or OOM bugs. So, at every point we report only one timeout and only one OOM bug per one fuzz target. Once that bug is fixed we may file another one, and so on. + +Currently we do not offer ways to change the memory and time limits. |