Ivan Fratric
Ivan Fratric
Hi, I was wondering if you managed to get the DLL to load on the fixed address and if that resolved your issues - it would also be useful to...
I see. That PT buffer size may indicate that a *lot* is happening inside your target function (for the sense of measure, PT buffer of 24MB could correspond to ~200...
Looks like the socket ended up in invalid state, but it's difficult to say which chain of events led to this. Perhaps custom_net_fuzzer is too strict about errors and the...
Ah, ok then, I didn't look into it much.
Not sure if that's what you mean, but you can always write a .bat script (or a Python script or whatever) that will restart the fuzzer if it stops for...
Note that you should remove the `-debug` flag from your command line when running afl-fuzz.exe. It is only meant to be used with drrun.exe directly and leaving it will prevent...
At what point does the error occur? During the dry run or when fuzzing already starts? I'm thinking that maybe, on invalid (fuzzed) samples, your target throws some custom exception...
Can't tell you much more than what you see from the error message (i.e. where it occured). Possibly your target hasn't closed the file at the end of the iteration,...
I'd need to see the full command line, but my guess would be that you're putting it in the wrong place. Note that WinAFL has two kinds of command line...
Winafl does not currently support the dumb mode. Most of the code should still be in there, but _at least_ the `run_target` function would need to be modified to support...