You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected to see string("00000") or some similar easy to read minimized crashing value. With go-fuzz this example would always return 00000.
What did you see instead?
Every time I re-ran it (deleting the testdata info before each run) I got different crashing values each time that were not very human friendly to read.
Thanks for reporting the issue; but I think we're already tracking this in (the slightly more general) #48129.
I'm closing here as a duplicate; I suggest you test your patch on the testcases in #48129 too, and reference that issue (as Updates, or Fixes, depending on what it does on the test cases there).
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, with the lastest gotip.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I was playing around with the new fuzz testing. I ran this fuzzing test:
What did you expect to see?
I expected to see
string("00000")
or some similar easy to read minimized crashing value. With go-fuzz this example would always return00000
.What did you see instead?
Every time I re-ran it (deleting the
testdata
info before each run) I got different crashing values each time that were not very human friendly to read.Here are some examples:
string("\xcf\xcf\xf1ou")
string("\u007f\u007f\xee\xee\xff")
string("oommw")
string("\x00\x1c\x17\x01\x80")
🌴 I hope you all are having a great quiet week!
The text was updated successfully, but these errors were encountered: