Corey Farwell
Corey Farwell
How to reproduce this: ``` export RUSTFLAGS="-Cllvm-args=-sanitizer-coverage-level=3 -Zsanitizer=address" ``` ```rust extern crate pulldown_cmark; fn main() { if let Ok(s) = std::str::from_utf8(b"\n:8\x02*>\n*\n\n\t\x02:\n\x0b\x12:
This might be because of https://github.com/rust-lang/rust/issues/39882 ?
Considering "ACCESS of size 0", I'm pretty sure this is https://github.com/rust-lang/rust/issues/39882
I'm planning on leaving this open until this gets fixed upstream in libfuzzer.
Sounds good to me. I won't be able to get to this, so if someone wants to work on it, go ahead! Once you open a PR, I can review...
I'd like to keep the arguments the same as Cargo and not try to invent anything new. So `cargo all-features `.
Sounds good to me. I won't be able to get to this, so if someone wants to work on it, go ahead! Once you open a PR, I can review...
@Manishearth Do you know which aspect of compiling with different feature flags causes `target/` to fill up? I'm open to your suggestion, but also wonder if there's a way we...
What about something like: ``` cargo build cp -R target target-cached for features in feature_flag_combinations: cargo build --features features rm -rf target cp -R target-cached target ```
Actually that's probably not good since features could have a ton of dependencies. Maybe the first line should be `cargo build --all-features`. Hmm