-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
cranelift-fuzzgen fuzzbug: "Floating-point-exception in cranelift_filetests::function_runner::CompiledFunction::call::h6386b90d4c398abf" #4760
Comments
Huh, I can't format this input:
|
Nevermind, forgot to base64 decode it 😅 Formatted
|
Ah, fuzzing... good to know we can use jump tables😆 |
This comment was marked as resolved.
This comment was marked as resolved.
OSS-Fuzz thinks this was fixed, and indeed, I can reproduce the SIGFPE on 9cb987c but not on d394edc. However I don't immediately see why #4752 would have actually fixed this. On top of that, the same input produces a new error now:
|
Okay, #4752 does not change the CLIF that this fuzz target generates, which is good: we didn't accidentally "fix" the fuzz bug by changing the input format. It does dramatically change the assembly generated from that CLIF, including making the stack frame slightly smaller and the function slightly larger. But both versions have almost 1,200 instructions and I don't have any hope of getting to a root cause from there. There's a So it's plausible enough that fixing shifts/rotates made this test case pass that I'm going to just declare that OSS-Fuzz is right, and this bug is fixed by that PR. Hooray! The new error is another matter which I'll bring up in #4667. |
https://oss-fuzz.com/testcase-detail/5258173635756032
input: here
cc @afonso360
The text was updated successfully, but these errors were encountered: