WorksButNotTested

AFL++ FRIDA mode does only support a single thread right now as that’s all I needed for my purposes. There are a few options though which you could pursue to...

Is this not equivalent to just setting `AFL_ENTRYPOINT` for you target or am I missing something?

Are you running with the version in the blog post? If so, please try the latest and see if the problem persists.

Could be related to this issue which was fixed. https://github.com/AFLplusplus/AFLplusplus/pull/1826

Using AFL_FRIDA_INST_DEBUG_FILE may help work out where things are crashing in your example. Also try adding prints to your harness code and commenting sections out to narrow down where the...

With frida mode, as soon as execution hits a function in an excluded range, coverage will stop until the function returns. Even if that function calls another in a region...

No, but you will want your harness to be included in coverage otherwise as soon as it starts running, it will execute the uninstrumented code until it returns. And so...

You should try and work with persistent mode if you can and the test case stability is OK. It is much faster. Also using the hook to provide input rather...

If you run with ‘ AFL_FRIDA_INST_DEBUG_FILE’ and ‘AFL_FRIDA_STALKER_ADJACENT_BLOCKS=0’ then you should see the exact blocks of executed code and the block which stalker generates written to the log file. Hopefully...

Also bear in mind when using GDB with FRIDA mode, when you set a breakpoint, the debugger is writing a trap instruction into the code (overwriting the point where you...