Ivan Fratric
Ivan Fratric
This could mean one of 2 things. - If we assume the instrumentation is working correctly, the message can be interpreted as "the target crashed before reaching the target function"...
For me, it shows as having a 2 tab indentation whereas the line before has a single tab.
Did you build the binary you are trying to instrument with /PROFILE linker flag. Also note that static instrumentation works only on 32-bit binaries (see https://github.com/googleprojectzero/winafl/blob/master/readme_syzygy.md)
Hi, on the newer Windows, you should be using the weekly DynamoRIO build from https://github.com/DynamoRIO/dynamorio/releases, *not* 8.0.0
Hm, if you're still having issues with the latest DR, then the only option is to either use an older Windows version or a different instrumentation backend. You can also...
I don't see the bug there - if `dll_mutate_testcase_with_energy_ptr` is NULL, won't it go to the `else if (dll_mutate_testcase_ptr)` branch?
in_app persistent mode is currently not supported with the Intel-PT coverage
Well, you could also add the support for in app persistent mode in winaflpt.c :-)
Strange that the log doesn't get created at all as creating the log file should be one of the first thing it does when -debug is specified. Can you verify...
If this really is due to some incompatiblity with DynamoRIO, an alternative is to try the newly released https://github.com/googleprojectzero/Jackalope. It uses completely different instrumentation so it might work better for...