Hitting Fork Server handshake Failed

[sbachchuwar]

I put my bzImage & kallsyms under kern/ & triggered runFuzz -M M0:
Getting aborted just on attempting dry run:

[*] Spinning up the fork server...

[-] Hmm, looks like the target binary terminated before we could complete a
handshake with the injected code. There are two probable explanations:

- The current memory limit (2.00 GB) is too restrictive, causing an OOM
  fault in the dynamic linker. This can be fixed with the -m option. A
  simple way to confirm the diagnosis may be:

  ( ulimit -Sv $[2047 << 10]; /path/to/fuzzed_app )

  Tip: you can use http://jwilk.net/software/recidivm to quickly
  estimate the required amount of virtual memory for the binary.

- Less likely, there is a horrible bug in the fuzzer. If other options
  fail, poke <[email protected]> for troubleshooting tips.

[-] PROGRAM ABORT : Fork server handshake failed
Location : init_forkserver(), afl-fuzz.c:2123

I also tried setting AFL_NO_FORKSRV=1, but didn;t help much:
[] Attempting dry run with 'id:000000,orig:ex1'...
[!] WARNING: Test case results in a crash (skipping)
[] Attempting dry run with 'id:000001,orig:ex2'...
[!] WARNING: Test case results in a crash (skipping)
[] Attempting dry run with 'id:000002,orig:ex3'...
[!] WARNING: Test case results in a crash (skipping)
[] Attempting dry run with 'id:000003,orig:ex4'...
[!] WARNING: Test case results in a crash (skipping)
[] Attempting dry run with 'id:000004,orig:ex5'...
[!] WARNING: Test case results in a crash (skipping)
[] Attempting dry run with 'id:000005,orig:ex6'...
[!] WARNING: Test case results in a crash (skipping)
[*] Attempting dry run with 'id:000006,orig:ex7'...
[!] WARNING: Test case results in a crash (skipping)

[-] PROGRAM ABORT : All test cases time out or crash, giving up!
Location : perform_dry_run(), afl-fuzz.c:2725

[mylamour]

Did you find way to solute it ?