>>> On 04.10.17 at 18:48, wrote:
> On 10/04/2017 09:23 AM, Jan Beulich wrote:
> On 25.09.17 at 16:26, wrote:
>>> x86.h := asm/x86-vendors.h asm/x86-defns.h asm/msr-index.h
>>> x86_emulate.h := x86_emulate_user.h x86_emulate/x86_emulate.h $(x86.h)
>>>
>>> -x86_emulate_user.o: x86_emulate_u
On 10/04/2017 09:23 AM, Jan Beulich wrote:
On 25.09.17 at 16:26, wrote:
>> --- a/tools/fuzz/README.afl
>> +++ b/tools/fuzz/README.afl
>> @@ -41,3 +41,17 @@ Use the x86 instruction emulator fuzzer as an example.
>> $ $AFLPATH/afl-fuzz -t 1000 -i testcase_dir -o findings_dir --
>> ./afl-ha
>>> On 25.09.17 at 16:26, wrote:
> --- a/tools/fuzz/README.afl
> +++ b/tools/fuzz/README.afl
> @@ -41,3 +41,17 @@ Use the x86 instruction emulator fuzzer as an example.
> $ $AFLPATH/afl-fuzz -t 1000 -i testcase_dir -o findings_dir --
> ./afl-harness
>
> Please see AFL documentation for mor
...to generate a "normal" coverage-instrumented binary, suitable for
use with gcov or afl-cov.
This is slightly annoying because:
- Every object file needs to have been instrumented to work
effectively
- You generally want to have both an afl-instrumented binary and a
gcov-instrumented b
