Age | Commit message (Collapse) | Author | Files | Lines |
|
* update all +build statements
Signed-off-by: MQasimSarfraz <syed.qasim.sarfraz@gmail.com>
* remove old +build style
Signed-off-by: MQasimSarfraz <syed.qasim.sarfraz@gmail.com>
|
|
This can't be used in its current form; revert the entire PR.
Revert "fuzzing: allow setup function to be called (#3175)"
This reverts commit 62451fd3eb68cef5dcdafe6e4228f08cf52d84fc.
|
|
* fuzz: use gofuzz build tag instead of fuzz
Since go-fuzz does not support Go modules yet, vendor dependencies.
Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
* fuzz: avoid vendoring code for go-fuzz
Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
|
|
This allows to fuzzing of more interesting targets that require setup.
Signed-off-by: Miek Gieben <miek@miek.nl>
|
|
No need to have this build all the time.
|
|
Fix file/fuzz.go build and docs in Makefile.fuzz
Each plugin can add a fuzz.go to join the fuzzing craze.
pkg/fuzz/do.go could be made a lot smarter, but is probably good enough
for starters.
$ make -f Makefile.fuzz <plugin>
will build with go-fuzz-build and then execute a go-fuzz run. Each
plugin's fuzz run uses a per-plugin directory to store the fuzz data.
|