You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cargo fuzz --version
cargo-fuzz 0.12.0
$ git clone [email protected]:rust-fuzz/libfuzzer.git && cd libfuzzer/example_mutator
$ cargo fuzz run boom
...
thread '<unnamed>' panicked at
...
If I install from git cargo install --git https://github.com/rust-fuzz/cargo-fuzz, it not longer panics nearly instantly (finds an input that is prefixed with "boom"). I suspect this is because fuzz_mutator is stripped due to #394. That said, I did notice stripping dead code fixed errors llvm-cov produced when I was trying to generating coverage reports.
More info:
If I compile the example in a standalone project without cargo-fuzz, I can reproduce the behavior more clearly.
Using the package from crates prior to #394:
If I install from git
cargo install --git https://github.com/rust-fuzz/cargo-fuzz
, it not longer panics nearly instantly (finds an input that is prefixed with "boom"). I suspect this is becausefuzz_mutator
is stripped due to #394. That said, I did notice stripping dead code fixed errorsllvm-cov
produced when I was trying to generating coverage reports.More info:
If I compile the example in a standalone project without cargo-fuzz, I can reproduce the behavior more clearly.
Next, add a
panic!();
tofuzz_mutator!
and run ./target/debug/example_mutator
. I get a crash at the inserted panic.If I remove
-C link-dead-code
, the panic isn't reached.The text was updated successfully, but these errors were encountered: