trailofbits/deepstate

--fuzz produces the same test each time unless run with --no_fork

agroce opened this issue · 3 comments

Sort of obvious, rand() is going to reproduce without changing the generator.

One solution would just be to force no_fork when doing --fuzz though there might be some use of forking I can't think of off hand.

@pgoodman opinions?

and as we've noted before, using rand() is probably not really optimal, but anyway

Eh, just issue a complaint and fail for now, can revisit if there's a real need to forking fuzzing

I think the title means to say "--no_fork" at the end?

Indeed. Though I'm curious what --fuzz --no_fuzz would do. Explode, probably.