expend20

Yeah also noticed this, with next code it leaks roughly 1GB at a time. ```rust use unicorn_engine::unicorn_const as ucc; use unicorn_engine::Unicorn; fn leaks() { let uni = Unicorn::new(ucc::Arch::X86, ucc::Mode::MODE_64); if...

> Yeah also noticed this, with next code it leaks roughly 1GB at a time. > > ```rust > use unicorn_engine::unicorn_const as ucc; > use unicorn_engine::Unicorn; > > fn leaks()...

hey @bet4it, thanks for the fix. I can confirm it's working (not leaking the memory on my sample)

if it's possible to add vectorized opcodes, it would be super cool ``` .text:00000001400017FA vmovdqu ymm0, cs:ymmword_140015960 .text:0000000140001802 vmovdqu [rbp+40h+var_20], ymm0 .text:0000000140001807 imul rax, [rbp+40h+var_40], 20h .text:000000014000180C mov rcx, [rsp+60h+arg_0]...

Hi @serpilliere! >and the flags You got it, all those examples are from ctfs :D > By the way, you can try to add yourself some semantics if you whish:...

hi, just specify full path for output directory. This will lead to passing full path to the target binary.

Hi, just as a raw thought. You probably can leverage -fuzz_iterations option to control the amount of leaked data before the process will be restarted.

I'm not @ifratric but there are only three instrumentation options: DR, syzygy and IntelPT :)

Instrumentation gives you coverage, AFL can't effectively work without coverage

Are there any benefits from binding threads to CPUs if you can't leverage `-thread_coverage` option? I.e. coverage hit thread is not the same as harness thread.