-
Notifications
You must be signed in to change notification settings - Fork 128
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
Bazel + junit Fuzz Tests #895
Comments
You can try to set Jazzer's JUnit integration does not create a dedicated reproduces, as it's quite easy to reproduce findings via JUnit IDE plugins. With those you can execute/debug only specific inputs. Currently, there is no dedicated, nor easy, way to pass on arguments to libfuzzer through JUnit fuzz tests. Apparently this works, but is less that ideal. |
@asudhak - was the suggestion from @bertschneider helpful? |
When running Junit Fuzz Tests triggered using
bazel test
libfuzzer appears to look for the.cifuzz-corpus
in a temp directory under/private/var/tmp/
and also places the crashes in a subdir of/private/var/tmp/
which gets purged after a run.Is there a right way of specifying a different directory for Jazzer/Libfuzzer to use for the corpus and the reproducers ?
Follow up question - similarly, how do you pass other Jazzer flags such as
--keep_going=N
when using junit/bazel ?The text was updated successfully, but these errors were encountered: