Taiki Endo

I'm happy to accept the patches needed to support cargo-fuzz. Btw, does cargo-fuzz not work in a way like cargo-afl? https://github.com/taiki-e/cargo-llvm-cov?tab=readme-ov-file#get-coverage-of-afl-fuzzers

> cp ./target/x86_64-unknown-linux-gnu/release/ ./target/release/ As for this `cp`, I guess passing `--target x86_64-unknown-linux-gnu` to `cargo llvm-cov report` should handle it well without this `cp`.

There is no limit on the number of flags to add, but it may be easier here to add one flag that is specific to integration with cargo-fuzz and handle...

First, as I said above, I'm open to accepting patches as needed for support. I cannot specify too specifically which forms are preferred at this time, as it depends on...

Thanks for the report! Is this a problem that only occurs when combined with nextest? Or is this a problem that also occurs when using cargo-llvm-cov without nextest? I have...

Does the [existing method](https://github.com/taiki-e/cargo-llvm-cov?tab=readme-ov-file#merge-coverages-generated-under-different-test-conditions) not work?

See https://github.com/rust-lang/rust/issues/124800 (coverage_nightly is listed in https://github.com/rust-lang/rust/issues/124800#issuecomment-2097123618). This lint will probably be allowed by default: https://github.com/rust-lang/rust/pull/124841

See cargo docs: https://doc.rust-lang.org/cargo/reference/workspaces.html#the-lints-table > ```toml > # [PROJECT_DIR]/Cargo.toml > [workspace] > members = ["crates/*"] > > [workspace.lints.rust] > unsafe_code = "forbid" > ``` > ```toml > # [PROJECT_DIR]/crates/bar/Cargo.toml >...

> Trying the following method so far does not generate the relevant *.profraw > ``` > cargo build # Build rust binaries. > # Commands using binaries in target/debug/*, including...

> * kill -9 Indicates related service processes AFAIK, SIGKILL is currently not supported. See https://github.com/taiki-e/cargo-llvm-cov/issues/235 for more.