HonngFuzz socketfuzzer backward compatibility

[ashishk1994]

Hi,

It looks like socketfuzzer/unittest.sh 's backward compatibility is broken. Can we fix it.

Evidences:

1. ) Last working commit:

commit 3f891ed683e4956e24dcd53b1215f96c372fff3d (HEAD)
Merge: dbb61a5a 0658eb7e
Author: jduart <jduart@users.noreply.github.com>
Date:   Tue Aug 27 10:03:37 2019 +0200

    Merge pull request #270 from neuracr/rss
    
    max_rss metrics

Results of bash unittest.sh

Waiting for SocketFuzzer connection on socket: /tmp/honggfuzz_socket.2969
Auto Test
connecting to /tmp/honggfuzz_socket.2969

Test: 0 - initial
A SocketFuzzer client connected. Continuing.
  ok: Fuzz

Test: 1 - expecting first new BB
# vulnserver_cov: New client connected
# vulnserver_cov: Received data with len: 6 on state: 0
# vulnserver_cov: Auth success
# vulnserver_cov: Closing...
# vulnserver_cov: Listening on port: 5001
  ok: Fuzz

2.) Commit just after it broke the results as following:

commit 99559afa16ca275e443e6111000407ff3a4de0e6 (HEAD)
Author: Robert Swiecki <robert@swiecki.net>
Date:   Tue Aug 27 22:45:02 2019 +0200

    subproc: allow to use ___FILE___ and -s with persistent mode

Results of bash unittest.sh

Waiting for SocketFuzzer connection on socket: /tmp/honggfuzz_socket.3530
Auto Test
connecting to /tmp/honggfuzz_socket.3530

Test: 0 - initial
A SocketFuzzer client connected. Continuing.
  nok:

[ashishk1994]

@robertswiecki @dobin can you please confirm and acknowledge this issue.

[ashishk1994]

@Mrmaxmeier I could see you have added the fix. did you get the chance to fix unittest too?

[robertswiecki]

Please re-open if there's still need to sync fixing this.