van Hauser

> It looks like there is some conflict between the implementation and the comments about ngram. According to the comment: > > ``` > /* "For efficiency, we propose to...

@Lancern I disagree. if there is an issue where the forkserver crashes - it needs to be fixed. however I dont know why it should crash. it does basically very...

@Lancern great so it is not a bug in the forkserver :) the correct solution is then to modify your target so that node::Kill(getppid(), SIGKILL)) cannot happend, e.g. bei return...

if it is optional and not a default and an env var (to save on command line parameters that we might need in the future) then why not

> I wonder another question: why is AFL_PERSISTENT discarded? I know AFL can automatically figure out whether the binary supports persistent mode, but what if the persistent signature is contained...

These could all be relevant: havoc_stack_pow2, custom_only, skip_deterministic, use_splicing, not_on_tty, no_arith, run_over10m, expand_havoc, n_fuzz, active_paths, var_bytes, queued_*, cycle_wo_finds, start_time, extras + extras_cnt, a_extras + a_extras_cnt, custom_mutators_count, the current queue entry...

is this fixed?

@hexcoder- @WorksButNotTested is this still an open issue or has it been resolved?

ok he can reopen it if it still doesnt work

I agree that the forkserver communicationis where this should be implemented. there should be a few bits unused.