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
This is not really an issue but I'd like to suggest specifying somewhere that the reproduce script will only work when fuzzers are built with the libfuzzer engine, since libfuzzer arguments are automatically passed to the binary (-rss_limit_mb=2560 -timeout=25)
There was some discussion about it in this issue a while ago: #4497 (comment)
Even better would be to detect the fuzzing engine when running reproduce and either emitting a warning or just running the binary without libfuzzer arguments if it detects something other than libfuzzer?
It could save some testers some time debugging the wrong binary.
Thanks again.
The text was updated successfully, but these errors were encountered:
Hi and thanks for a great tool,
This is not really an issue but I'd like to suggest specifying somewhere that the
reproduce
script will only work when fuzzers are built with thelibfuzzer
engine, sincelibfuzzer
arguments are automatically passed to the binary (-rss_limit_mb=2560 -timeout=25
)There was some discussion about it in this issue a while ago: #4497 (comment)
Maybe writing a note about it in https://github.com/google/oss-fuzz/blob/masterdocs/advanced-topics/reproducing.md
Even better would be to detect the fuzzing engine when running
reproduce
and either emitting a warning or just running the binary without libfuzzer arguments if it detects something other than libfuzzer?It could save some testers some time debugging the wrong binary.
Thanks again.
The text was updated successfully, but these errors were encountered: