Josh Bleecher Snyder
Josh Bleecher Snyder
I often find myself repeating code like this: ```go var verbose bool func init() { all := []*flag.FlagSet{ /* list of FlagSets for different sub-commands and sub-sub-commands */ } for...
While fuzzing something, I got this crash: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x8 pc=0x10210d414] goroutine 1 [running]: go-fuzz-dep.serialize({0x0, 0x0},...
I propose that we add a paragraph to the top of the readme declaring go-fuzz unmaintained, and then Archive the repo on GitHub. cc @dvyukov @thepudds @mvdan
Juggling multiple fuzz functions is an annoyance. Currently you have to compile O(n) times, track O(n) zip files, and run O(n) go-fuzz instances using O(n) distinct workdirs. I'd rather compile...
In #249, @dvyukov wrote: > Re CoverTab, it always was supposed to be of tunable size. It's just that I did fixed 64K initially as the simplest option and then...
It'd be nice if we could embed the support packages go-fuzz-build needs into the binary, rather than relying on the go tool being able to find them on disk. See...
cc @thepudds @mvdan
[broken out from discussion in #273] It'd be better to do as std does with testing and emit an executable instead of a zip file and using an external runner....
The current Fuzz function signature is ```go func FuzzSomething(b []byte) int ``` I think we should migrate it to something more like: ```go import fuzz "github.com/dvyukov/go-fuzz" func FuzzSomething(fz fuzz.F) ```...
I have work in progress improving literal collection. This issue is to discuss design decisions in advance of sending PRs. * The current design converts int literals to strings during...