Tags: thepudds/fzgen
Tags
multiple corpus locations as input to fuzzing, and change default out… …put corpus location (#7) See PR #7 comment for details. * fuzzing_rich_signatures.txt: multiple corpus locations as input to fuzzing, change default dest * main.go: multiple corpus locations as input to fuzzing, change default dest * cache.go: multiple corpus locations as input to fuzzing, change default dest * richsig.go: multiple corpus locations as input to fuzzing, change default dest * richsig_test.go: multiple corpus locations as input to fuzzing, change default dest * exec.go: multiple corpus locations as input to fuzzing, change default dest * packages.go: multiple corpus locations as input to fuzzing, change default dest
directly manage randomness for rich signatures, which also enables li… …teral injection (#6) * fuzzing_rich_signatures.txt: enable harder test that requires guessing 64-bit number via rich signature * travis: install goimports * fuzzing_rich_signatures: check for goimports * bytes2rand.go: directly manage randomness for rich signatures * bytes2rand_test.go: directly manage randomness for rich signatures * randparam.go: directly manage randomness for rich signatures * randparam_test.go: directly manage randomness for rich signatures * exec.go: directly manage randomness for rich signatures * richsig.go: directly manage randomness for rich signatures * richsig_test.go: directly manage randomness for rich signatures
use corpus as deterministic unit tests when not fuzzing (#3) * main.go: prepare for deterministic corpus execution * flag.go: prepare for deterministic corpus execution * flag_test.go: prepare for deterministic corpus execution * runcorpus.go: initial commit, executes corpus as unit tests * packages.go: prepare for deterministic corpus execution * verify_corpus: initial commit, test deterministic corpus execution * readme: add mention of new ability to use corpus as deterministic unit tests * readme: update usage example to mention corpus as unit tests