3 ms·
Anyone seen good articles on converting go-fuzz tests to native fuzzing? Specifics on the new corpus format and a converter from go-fuzz would be really useful
by ryanschneider 5y ago
Anyone seen good articles on converting go-fuzz tests to native fuzzing? Specifics on the new corpus format and a converter from go-fuzz would be really useful.
It’s great to hear that the fuzzer is built on go-fuzz so hopefully the conversion process won’t be too bad: https://github.com/dvyukov/go-fuzz/issues/329 https://github.com/dvyukov/go-fuzz/issues/329
- morelisp 5y agoI've pre-emptively migrated a couple projects and found that loading the old corpus files wherever you already had them and then `Add`ing them as whatever new appropriate type was the easiest way. The inclusion of types necessitates at least a minor migration. I did not find any official documentation on the format, though it's trivial to read, e.g.: go test fuzz v1 string("\xff0") Overall while the API (and of course tooling) is a huge step forward, corpus management feels like a small step backwards compared to go-fuzz - I didn't find a way to pull non-crashers into an in-repo corpus other than manually copying them out of my cache directory. And one-file-per-case still blows up a lot of repo management tools.
- aleksi 5y agohttps://pkg.go.dev/golang.org/x/tools@v0.1.8/cmd/file2fuzz https://pkg.go.dev/golang.org/x/tools@v0.1.8/cmd/file2fuzz