Ivan Fratric

This is the error in this case: ``` [!] WARNING: Process exit during target function ``` However, I can't tell what happened before the process exited. Since I'm seeing things...

Hi, I can't help with your target, but you can test the in_app persistent mode as described in https://github.com/googleprojectzero/winafl/blob/master/readme_dr.md#in-app-persistence-mode and report if you encounter problems with that. But also, you...

It seems there are some issues with DynamoRIO on the latest windows where calling some Windows API functions (e.g. `OpenFileMapping` which is needed for coverage map) results in the process...

Does it work if you use absolute path to `custom_net_fuzzer.dll`

Are you using DR or TinyInst backend, With DR, setting `AFL_NO_SINKHOLE` environment variable should do the trick, see https://github.com/googleprojectzero/winafl/blob/master/afl-fuzz.c#L8513 With TinyInst, AFAIK it should already be priniting to stdout.

Sure, I can update the documentation later, but for now here is a quick example: To run the server ``` ./fuzzer -start_server 127.0.0.1:8337 -out serverout ``` Then, to run the...

You can usually better debug these issues by running your target under litecov.exe (part of TinyInst) with the same instrumentation parameters that you use for fuzzing.

`winafl.dll` can't be used without afl-fuzz, unless it's in debug mode, in which case it must be used *without* afl-fuzz. So that explains the "error connecting to pipe" as well...

Additionally, you seem to be using -persistence_mode in_app incorrectly. It's only meant to be used if your target already loops on its own over the target function. WinAfl's `test.exe` can...

The run with litecov also seems wrong, you are getting `process exit during target method` which is unexpected. I suggest trying with `-target_method main` instead of `-target_offset`. If it still...