Skip to content
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

driver: Do not prepare for a subprocess for -fork=0 #758

Merged
merged 1 commit into from
Jun 6, 2023
Merged

Conversation

fmeum
Copy link
Contributor

@fmeum fmeum commented Jun 6, 2023

-fork=0 and similar flags disable the respective libFuzzer modes and thus should not lead Jazzer to prepare for being run in a subprocess, e.g., not set -seed.

Fixes #756

`-fork=0` and similar flags disable the respective libFuzzer modes and
thus should not lead Jazzer to prepare for being run in a subprocess,
e.g., not set `-seed`.
@fmeum fmeum requested a review from a team June 6, 2023 06:55
@fmeum fmeum enabled auto-merge (rebase) June 6, 2023 06:58
@fmeum fmeum merged commit c29e73c into main Jun 6, 2023
9 checks passed
@fmeum fmeum deleted the FUZZ-709-fork-0 branch June 6, 2023 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using -fork=0 will trick Jazzer to use subprocesses
2 participants