Description
I am not sure if this is technically and issue with honggfuzz-rs or some other part of the pipeline, but I noticed that when using the memory sanitizer, there will always be at least 1 unique failure even if using an empty fuzz target.
To reproduce, use this fuzz target:
fuzz!(|_data: &[u8]| { return });
run it with the memory sanitizer:
RUSTFLAGS="-Z sanitizer=memory" cargo hfuzz run hfuzz
will get one unique error:
Crash (dup): 'hfuzz_workspace/hfuzz/SIGABRT.PC.7ffff7dc6755.STACK.192f69358f.CODE.-6.ADDR.(nil).INSTR.mov____0x108(%rsp),%rax.fuzz' already exists, skipping [2019-10-09T23:26:46-0700][W][28005] arch_checkWait():248 Persistent mode: pid=28308 exited with status: SIGNALED, signal: 6 (Aborted)
When running in debug, the actual error is: Uninitialized bytes in __interceptor_memchr at offset 0 inside [0x701000000000, 4 and it doesn't give a backtrace.