`--log-level` doesn't work

I'm running grcov $(find . -name 'cargo-test-*.profraw' -o -name '*.gcno' -o -name '*.gcda') --binary-path ./target/testnet/deps -s . -t html,lcov --branch --ignore-not-existing -o html42-deps --log-level DEBUG --log stdout

And the only output I get is

[2023-04-25 10:04:46] 10:04:46 [ERROR] A panic occurred at /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/grcov-0.8.18/src/producer.rs:504: Cannot load file '"/builds/TriplEight/target/debug/build/eyre-283ea9182ebd0eaf/build_script_build-283ea9182ebd0eaf.gcda"': it isn't a .info, a .json or a .xml file.
[2023-04-25 10:04:48] 10:04:48 [ERROR] A panic occurred at /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/grcov-0.8.18/src/producer.rs:504: Cannot load file '"/builds/TriplEight/target/debug/deps/chacha20poly1305-0942dab31ea37fd3.gcno"': it isn't a .info, a .json or a .xml file.
exit code 123

Tried different options for --log-level and --log flags, but nothing helped. The only way I could come up with to get the logs is strace -f grcov ..., but it's a pain to dig through.

It would be helpful to see gcov output like here: https://users.rust-lang.org/t/howto-generating-a-branch-coverage-report/8524/11

Start by tracing how the CLI handles --log-level and --log, then inspect the panic reported at producer.rs:504 while processing .gcda and .gcno files. Reproduce the command from the issue and compare the available logging output with the requested gcov output; done means the flags provide the expected diagnostic logs without requiring strace.