2 ms·
FWIW older design documents have (some) reasoning for integrating fuzzing natively: - https://docs.google.com/document/d/1N-12_6YBPpF9o4_Zys_E_ZQndmD06wQVAM_0y
by masklinn 5y ago
FWIW older design documents have (some) reasoning for integrating fuzzing natively:
- https://docs.google.com/document/d/1N-12_6YBPpF9o4_Zys_E_ZQndmD06wQVAM_0y9nZUIE/pub https://docs.google.com/document/d/1N-12_6YBPpF9o4_Zys_E_ZQn...
- https://go.googlesource.com/proposal/+/master/design/draft-fuzzing.md https://go.googlesource.com/proposal/+/master/design/draft-f...
One of the original proposals (https://docs.google.com/document/u/1/d/1zXR-TFL3BfnceEAWytV8bnzB2Tfp6EPFinWVJ5V4QC8/pub https://docs.google.com/document/u/1/d/1zXR-TFL3BfnceEAWytV8...) further explains why, by apparently go-fuzz maintainers team (per issue 329[0] none of them seems in any way broken-hearted about the idea of deprecating go-fuzz eventually):
> go-fuzz suffers from several problems:
> - It breaks multiple times per Go release because it's tied to the way go build works, std lib package structure and dependencies, etc. It broke due to internal packages (multiple times), vendoring (multiple times), changed dependencies in std lib, etc.
> - It tries to do compiler work regarding coverage instrumentation without compiler help. This leads to build breakages on corner case code; poor performance; suboptimal quality of coverage instrumentation (missed edges).
> - Considerable difficulty in integrating it into other build systems and non-standard contexts as it uses source pre-processing.
> Goal of this proposal is to make fuzzing as easy to use as unit testing.
[0] https://github.com/dvyukov/go-fuzz/issues/329 https://github.com/dvyukov/go-fuzz/issues/329