winafl
winafl copied to clipboard
Unexpected result from pipe! expected 'P', instead received 'C'
update windows to version 1809(17763.107), which can cause process run error:
[-] PROGRAM ABORT : Unexpected result from pipe! expected 'P', instead received 'C'
Location : run_target(), c:\work\winafl\source\afl-fuzz.c:2635
because target process crash, it's a winafl bug.
it has sloved after restore old windows version.
Hey, I heard recently of a similar (but not quite the same) issue, also on Windows 10. Could you tell me
- What DynamoRIO version you are using
- Does the issue occur immediately or after fuzzing correctly for some time?
- Does the issue occur when fuzzing on a single instance or only when running multiple fuzzer instances in parallel?
- DynamoRIO 6.2.0-2 2.occur immediately 3.single instance
Ah, it's a different error than the one I saw previously then. But DynamoRIO 6.2.0-2 is quite old and doesn't play nicely with the recent versions of Windows 10 sometimes. Could you try with DynamoRIO 7.1 and see if the problem persists (note that the recent pre-built binaries were compiled with this version as well). If the problem persists, could you run the debug mode as described in https://github.com/googleprojectzero/winafl/blob/master/readme_dr.md and post the log.
I got a DynamoRIO notice with DynamoRIO 7.1 in the debug mode:
Client library targets an incompatible API version and should be re-compiled
then process exit.
it also run error after re-complied my 32-bits exe with win10 sdk 10.0.17763.0. But it's normal to run exe directly.
Just to make sure, when compiling, did you also use DynamoRIO 7.1?
I make test.exe, no winafl. I already use the lasted winafl.
Hmm, AFAIK Client library targets an incompatible API version and should be re-compiled
means that the DynamoRIO versions of drrun.exe and winafl.dll are incompatible. I'm not sure how recompiling test.exe could have an effect on this. :-(
The last thing to try would be to compile both DynamoRIO and WinAFL yourself, that way everything should be set up for the Windows version you're using.
I'm having the same issue, do you fix it?