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
runtime: SIGABRT with while fuzzing #22033
Comments
I've a feeling this has to do with allocating too much memory, but I just wanted to make sure. I get this with some regularity while fuzzing. Usually it happens with a "large" decimal like |
We need more information. I don't see a bug here; I see a program that was running normally but was killed because it ran for more than 10 seconds. Are you saying that the program should have terminated sooner? |
Right, this issue gave me pause enough to create an issue here. What more information is needed to determine whether this is an actual bug or just an overreaction on my part? |
The fuzzer doesn't really use the runtime much. It just calls your function with different inputs. So the first step would be to figure out which input the fuzzer is passing to your code. Then figure out what your code is doing with that input. Why did it take more than 10 seconds? It should be possible to recreate the problem without the fuzzer being involved at all. |
@ianlancetaylor Sorry, I should've thought this though more than I did last night. |
What version of Go are you using (
go version
)?1.9
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?GOOS=darwin
GOARCH=amd64
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Running the following through
go-fuzz
What did you expect to see?
Program run normally.
What did you see instead?
The text was updated successfully, but these errors were encountered: