[LINUX remote pid] Both ends monitoring about honggfuzz HOT 1 CLOSED

After playing with a few approaches it is not worth paying the cost of monitoring both ends from the same fuzzing campaign. Plus the fact that things get super complex/expensive when fuzzing with coverage/feedback since runtime data structures need to maintained twice.

For now I've solved this problem by running two campaigns in parallel: one attaching to long-lived server process and one spawning new fuzzer clients. I've written a small intermediate program to do the negotiation work between the two ends letting the long-lived fuzzer know when a new seed has been selected from the other end (pretty much an external preparation process wrapper).

Long story short, I don't think it's worth it to upstream such a feature. Thus closing.

from honggfuzz.