I spent an hour right now trying to debug error connecting to pipe on test run without afl-fuzz. It occured that I forgot the -debug option. While the whole thing is kinda obvious, if you need test run then you shouldn't forget the -debug, a suggestion about it on pipe error would've been very helpful.

What I propose is to edit error message so it would be `error connecting to pipe (did y

As we've found in rust-lang/rust#36705, jemalloc has abysmal fork performance in some kernel configurations, notably on recent Ubuntu versions.

Even on good configurations system default allocator has about 20% better fork performance than jemalloc.

This can be done in documentation, by adding the 2 lines described in https://doc.rust-lang.org/nightly/book/custom-alloc

Section 3.4 of the paper describes using gradient descent with a 2-point method for computing the gradient vector. This basically involves doing O(d) function calls to find the approximate gradient then doing a small number of calls to move in that direction. There is a long history of Derivative free Optimization Methods, that try to make each function evaluation do some of both. For example so

@vlsi mentioned this in jlink/jqwik#84:

I guess it would make code easier to follow if you called GuidedFuzzing#getCurrentGuidance in JQF.java and passed it to new FuzzStatement(...).

This is a good suggestion, and can be easily implemented to make the code more understandable.