e4298ccf31
The max input size is 16384, so in case the input is saved after each run, then this can allocate ~300MB of memory. This is considerable amount, given that the upper limit of the fuzzer process is 2GB. Signed-off-by: Miklos Vajna <vmiklos@collabora.com> Change-Id: Ieedb6a537d5b539255ed8bacd79ff23db3c15e9f |
||
---|---|---|
.. | ||
admin-data | ||
data | ||
httpecho-data | ||
httpresponse-data | ||
Admin.cpp | ||
ClientSession.cpp | ||
httpecho-fuzz.sh | ||
HttpEcho.cpp | ||
HttpResponse.cpp | ||
README |
These fuzzers are meant to be built and executed inside lode.git's sanitizers environment (currently enables both asan and ubsan). online.git can be built the usual way, just the additional `--enable-fuzzers` flag is needed to build the fuzzers. It is useful to do this in a separate build tree, since the fuzzers config doesn't produce a `coolwsd` binary. Run the fuzzers like this: - Admin: ---- ./admin_fuzzer -max_len=16384 fuzzer/admin-data/ ---- - ClientSession: ---- ./clientsession_fuzzer -max_len=16384 fuzzer/data/ ---- - HttpResponse: ---- ./httpresponse_fuzzer -max_len=16384 fuzzer/httpresponse-data/ ---- - HttpEcho: ---- ./httpecho_fuzzer -max_len=16384 fuzzer/httpecho-data/ OR, better: ./fuzzer/httpecho-fuzz.sh ----