- 
                Notifications
    You must be signed in to change notification settings 
- Fork 819
Improve fuzzing of Two #8006
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
base: main
Are you sure you want to change the base?
Improve fuzzing of Two #8006
Conversation
        
          
                scripts/fuzz_opt.py
              
                Outdated
          
        
      | # The reduce.sh script will then do the right thing, using that as the first | ||
| # wasm, and reducing on the second one, if you replace "original.wasm" in the | ||
| # command with "second.wasm" as needed. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean replacing "original.wasm" in the text of reduce.sh? If not, which "original.wasm" is this referring to?
It would be useful to print these instructions in the fuzzer error message that provides the reduction command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"original.wasm" appears in the command that the fuzzer tells you to run. I clarified this now.
        
          
                scripts/fuzz_opt.py
              
                Outdated
          
        
      | # Generate a second wasm file. (For fuzzing, we may be given one, but we | ||
| # still generate it to avoid changes to random numbers later; we just | ||
| # discard it after.) | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment doesn't quite agree with the code below, which only generates the second module when it is not given.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yes, we only prepare to generate it. The actual generation consumes no randomness here. I clarified the text now.
I finally found out how to make this not horrible:
the second file is provided (or else reductions can fail weirdly).
BINARYEN_FIRST_WASMis provided (which means the first is to be kept fixed).