Bug: FuzzTests are sometimes throwing away unrecognized bytes

[awalterschulze]

dvyukov/go-fuzz#76

[awalterschulze]

https://github.com/gogo/fuzztests
More work is required.

[awalterschulze]

@dvyukov
I fixed some fuzz tests for the generated unmarshaler
e8b9b26#diff-6bca0143efa485acde512d77ff13d42f
Like so
e8b9b26#diff-e0188cb7643b9790acd32abc395a5659
That these fuzztests found
https://github.com/gogo/fuzztests/tree/dd8509cb52dd1c848ba92335cff036fb6a6ac3d1

I did find that I could shrink the examples quite a bit to produce the same error.
If you look at TestFuzzSint64Overflow you can see the original bytes that produced the error commented out and the input bytes I used to reproduce the error which is a subset of the bytes in the original.

[dvyukov]

@awalterschulze Thanks, filed dvyukov/go-fuzz#100

[awalterschulze]

Fixed another fuzz test failure
2093b57
Found using this version of the fuzztests
https://github.com/gogo/fuzztests/tree/e62df375312286dd3e1e65abffef3a3407dcd6b0

[awalterschulze]

Maybe I am missing something
golang/protobuf#77

[awalterschulze]

golang/protobuf#76

[awalterschulze]

I think there has been enough fuzzing for now.
Comparing the errors from golang and gogo protobuf would be the next thing to do, but I think at least the current generated code is better now.