BadInputs cause unexpected behavior
Closed this issue · 1 comments
kulgg commented
Description
You can find bad inputs with corresponding stack trace in unique_min_crashes and the byte input files in CrashesDeduplicatedMinimized:
kulgg commented
Just to add, since i'm done with fuzzing this: If anybody wants to fuzz test in the future i pushed my NHapi-Fuzz-Environment