On 23/04/2019 11:12, Caccavale, Samuel wrote:
> Yes. Current staging resolves all of the SIG-ILL related crashes.
>
> Tangentially I have ~1000 crashes which fail the `ctxt->regs->r(ip) ==
> orig_ip'
> assert at x86_emulate/x86_emulate.c:9862 when compiling afl-harness statically
> with afl-clang
Yes. Current staging resolves all of the SIG-ILL related crashes.
Tangentially I have ~1000 crashes which fail the `ctxt->regs->r(ip) == orig_ip'
assert at x86_emulate/x86_emulate.c:9862 when compiling afl-harness statically
with afl-clang-fast. They do not reproduce when compiled dynamically or
On 23/04/2019 10:10, Caccavale, Samuel wrote:
> My mistake, I'm currently unable to reproduce the ~100 crashes
> AFL found while fuzzing the master branch, on the current staging
> branch. It seems some staged patch has since addressed this.
>
> If it is of any interest, most of the crashes came
My mistake, I'm currently unable to reproduce the ~100 crashes
AFL found while fuzzing the master branch, on the current staging
branch. It seems some staged patch has since addressed this.
If it is of any interest, most of the crashes came from AVX512
instructions.
Sorry and thanks,
Sam
On 18/04/2019 16:02, Sam Caccavale wrote:
> As of now, the x86_instruction_emulator will execute opcodes
> belonging to CPU extensions that the host may not have.
> Specifying --ignore-sigill when running afl-harness will ignore
> all SIG_ILL including those generated by the above issue.
Which ins
As of now, the x86_instruction_emulator will execute opcodes
belonging to CPU extensions that the host may not have.
Specifying --ignore-sigill when running afl-harness will ignore
all SIG_ILL including those generated by the above issue.
---
.../fuzz/x86_instruction_emulator/afl-harness.c | 17 ++
