aboutsummaryrefslogtreecommitdiffhomepage
path: root/projects/croniter
diff options
context:
space:
mode:
authorGravatar DavidKorczynski <david@adalogics.com>2022-06-15 10:28:46 +0100
committerGravatar GitHub <noreply@github.com>2022-06-15 10:28:46 +0100
commitb9eac4e6517158d7d018b6d9a16384a872b3b4e8 (patch)
tree3de860a198ad559ac80ac16e82ec109b7d173774 /projects/croniter
parentf7c858041220523481dc79afdcf6f77074a3ea59 (diff)
croniter: instrument fuzzing function (#7865)
* croniter: instrument fuzzing function The Croniter build is having some troubles with coverage and I'm not entirely sure why. It seems like the corpus is not there and I'm not entirely sure if this has to do with some instrumentation underlyings. Locally the end-to-end process of running, collecting seeds and generating coverage works for me. The effort in this PR is to make the setup similar to pyyalm where the coverage visualisation works -- the only difference I could spot between fuzzers from the two projects is that croniter does not have its fuzzer entry function instrumented. * Instrument all. This is similar to protobuf-python
Diffstat (limited to 'projects/croniter')
-rw-r--r--projects/croniter/fuzz_iter.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/projects/croniter/fuzz_iter.py b/projects/croniter/fuzz_iter.py
index 7ba559bf..c0a5199a 100644
--- a/projects/croniter/fuzz_iter.py
+++ b/projects/croniter/fuzz_iter.py
@@ -26,6 +26,7 @@ with atheris.instrument_imports():
)
+@atheris.instrument_func
def TestOneInput(data):
fdp = atheris.FuzzedDataProvider(data)
base = datetime(2012, 4, 6, 13, 26, 10)
@@ -45,6 +46,7 @@ def TestOneInput(data):
def main():
+ atheris.instrument_all()
atheris.Setup(sys.argv, TestOneInput, enable_python_coverage=True)
atheris.Fuzz()