jonathanmetzman
jonathanmetzman
gcbrun trial_build.py skcms log4j2 --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz
/gcbrun trial_build.py skcms log4j2 --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz
/gcbrun trial_build.py jackson-core --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz
/gcbrun trial_build.py jackson-core --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz --force-build
/gcbrun trial_build.py skcms log4j2 --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz
/gcbrun trial_build.py jackson-core --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz --force-build
/gcbrun trial_build.py jackson-core --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz --force-build
/gcbrun trial_build.py jackson-core --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz --force-build
Worth landing this as it will make debugging easier
> Interesting : the fuzz target spends quite a bit of time resetting/clearing hash tables... which is not what they are optimized for and is needed by the fuzz target...