expend20

> or one that adds a switch for not using the affinity behavior at all It's already possible via AFL_NO_AFFINITY=1 environment variable. Thanks guys!

Hey guys, very interesting topic. Let me ask you some question. If the fuzzed program had heap OOB write and that write is handled by try/except block correctly without crashing,...

Another raw thought: there is no tools to catch stack OOB read afaik. So, developing one would lead to some good catches, probably :)

Ok, thanks a lot! Fixing image bases of dlls might be a temporarily solution. Feel free to close the issue ;)

> Which Windows version, which CPU and are you running inside a VM? btw, what is architecturally preventing it from running inside of a VM?

which gen of i7?

or you can patch the binary to jump on return

For the record, the problem indeed exist, here is the walkthrough ### How to repro ```c++ #include extern "C" { __declspec(dllexport) void fuzz_function(const char *src, size_t len) { char buf[512];...

> But then we need to just handle C0000409 exception, cause UnhandledExceptionFilter() will lead to VEH handler anyway (presumably, need to verify). Confirmed, VEH handler is called if `IsProcessorFeaturePresent(23)` return...

> Confirmed, VEH handler is called if IsProcessorFeaturePresent(23) return false Actually I was wrong, it's not the case. I confused it with exit process code 😆 Anyway I'll try to...