-
Hi, When an OOM is produced as part of fuzzing, no reproducer-code is generated. When you are using a Is there an example of how to read the data so that it can be used to re-run the fuzzing-target with this data? When I try to use the Base64 encoded string that is printed together with a
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
We recommend using the JUnit 5 support to write your fuzz test. Even with OOM crashes, you can run and debug all collected If that doesn't work, you can use the Jazzer replayer to run a given fuzz test class on a given |
Beta Was this translation helpful? Give feedback.
We recommend using the JUnit 5 support to write your fuzz test. Even with OOM crashes, you can run and debug all collected
crash-*
files directly as regular parameterized unit test cases. Existing fuzz tests can be reused with essentially no changes (just add@FuzzTest
and move them to a test class).If that doesn't work, you can use the Jazzer replayer to run a given fuzz test class on a given
crash-*
file. We have deprecated it in favor of the JUnit approach, but it should continue to work.