Corey Farwell

I think the best strategy here is to make a change to rustc to add in [the afl LLVM pass](https://github.com/mcarpenter/afl/blob/master/llvm_mode/afl-llvm-pass.so.cc) behind a rustc debug flag. Relevant IRC rust-internals discussion: https://botbot.me/mozilla/rust-internals/2017-02-26/?msg=81593902&page=3...

> What's the advantage of afl over libfuzzer? In my opinion, the UI is a lot more informative and easier to understand: http://lcamtuf.coredump.cx/afl/status_screen.txt . Also from what I've seen, there's...

okay, incorporating afl into cargo-fuzz is now doable. yesterday, i opened [this issue](https://github.com/rust-lang/rust/issues/45762) in rust-lang/rust. i was informed by @alex in that thread that it's now possible to use afl...

Published afl.rs 0.2 yesterday: https://users.rust-lang.org/t/announcing-afl-rs-0-2-bindings-for-american-fuzzy-lop/13981 which should make it easier to complete this issue now

The only way I know of would be to have `cfg` blocks on the visibility keywords so they're conditionally public or private, but that's pretty hacky and messy. Ideally, Rust...

Would be nice to get this working natively on macOS. That might just need an LLVM bump, not really sure.

since you ran `cargo +nightly fuzz run fuzz_target_1`, you're using nightly rust. can you run `cargo +nightly -Vv` to find out how recent your rust nightly is?

strange, it's all working for me on the same nightly, though on macOS

> @whitequark: you added a misspelled issue label, perhaps you want to fix it for future reference. fixed! thanks for pointing it out

> Would you accept a PR for a new subcommand that is specifically to feed additional data into the corpus folder? Absolutely! I don't see why not 👐