I am getting a stack-use-after-free violation from ASAN in a Rust fuzzing harness that does not reproduce with run-debug. The violation is not triggered immediately with a small/empty input if I add -C opt-level=0 to RUSTFLAGS. Two questions:
Is there a way to run the input through the same binary as hfuzz run? Ideally, I could also run without attaching to a debugger automatically.
Is there a known issue in Rust that could be causing non-reproducible or FP ASAN violations?