mirror of https://github.com/google/oss-fuzz.git
b9eac4e651
* 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 |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| build.sh | ||
| fuzz_iter.py | ||
| project.yaml | ||