Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: fuzz minimizing line gives a misleading number of bytes #48989

Closed
katiehockman opened this issue Oct 14, 2021 · 1 comment
Closed

cmd/go: fuzz minimizing line gives a misleading number of bytes #48989

katiehockman opened this issue Oct 14, 2021 · 1 comment
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@katiehockman
Copy link
Contributor

From #48884 @mvdan

func FuzzFoo(f *testing.F) {
	f.Fuzz(func(t *testing.T, n uint8) {
		if n%3 == 0 {
			t.Fatal("boom")
		}
	})
}
$ go test -fuzz=.
warning: starting with empty corpus
fuzz: elapsed: 0s, execs: 0 (0/sec), new interesting: 0 (total: 0)
fuzz: minimizing 26-byte crash input...
fuzz: elapsed: 0s, minimizing
--- FAIL: FuzzFoo (0.10s)
    fuzz_test.go:8: parent f.Logf

The fuzz: minimizing 26-byte crash input... line is wrong. It is minimizing a uint8, so there's no way that could be 26 bytes. Let's fix that, or just remove that line so it isn't misleading.

/cc @golang/fuzzing

@katiehockman katiehockman added NeedsFix The path to resolution is known, but the work has not been done. fuzz Issues related to native fuzzing support labels Oct 14, 2021
@katiehockman katiehockman added this to the Go1.18 milestone Oct 14, 2021
@gopherbot
Copy link

Change https://golang.org/cl/361414 mentions this issue: internal/fuzz: improve minimizing message

@golang golang locked and limited conversation to collaborators Nov 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: No status
Development

No branches or pull requests

2 participants