diff options
author | Yifan Hong <elsk@google.com> | 2020-04-28 23:39:05 -0700 |
---|---|---|
committer | Yifan Hong <elsk@google.com> | 2020-04-30 23:05:36 -0700 |
commit | 90a9393ea04ca4e40b07d94ddc6336ba6228db5e (patch) | |
tree | 0557597c9ef0caaedd0c123383ba8c16c0c67316 /trusty/coverage/coverage_test.cpp | |
parent | 5eb2d6fa27f5e92032ad61c9b674af5f7344f19b (diff) |
libsnapshot_fuzzer: use protobuf
Use protobuf because it already has all the fuzzing implemenetations.
Delete fuzz_utils.
Pros:
- Fuzzing protobuf is faster; it is easy to achieve 4K exec/s
- It is more guided; protobufs are fuzzed using mutators, and mutators
should have better knowledge of the structure of the fuzz data
- No more hand-written parsing code of the fuzz data. That code in
fuzz_utils.h is deleted.
- Corpus data can be reused even after adding new fields in the protobuf
- Corpus data is human-readable and easily manually written (it is
the text format of the protobuf)
Cons:
- The "actions" are "declared" in protobuf definition and "defined" in
C++, so there's more boilerplate to write. Adding a new "Action"
requires changes in both.
Test: run libsnapshot_fuzzer
Bug: 154633114
Change-Id: Idc2a6b2c087e370e4cfef53142a244b9b275389e
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions