Mark Thebridge

I have the same issue - but I can workaround it, because if I run `cargo count -a --exclude=$(cat .gitignore)` everything works as expected. Which suggests it's the gitignore handling...

Thanks for the speedy reply! It doesn't matter whether I'm using `LCOV_EXCL_START` or not, and yes it's 100% consistent - always fails on master, always works with v33...

Yes. I just manually checked out those two revs and compared. On e620da4: ``` $ cargo kcov error: failed to get coverage caused by: signal: 11 ``` On 860a324: ```...

Hmm - if I set debug=15 then both cases fail! The previously working case gives me: ``` $ cargo kcov -- --debug=15 > kcov_debug.out error: failed to get coverage caused...

No problem about the delay - enjoy your redecorating! You're right - running it with debug causes kcov itself to crash, and I do get a core. Output from loading...

Well, `libcore/lib.rs` is from the core Rust library, so not something I have my own copy of. I imagine it's [this file](https://github.com/rust-lang/rust/blob/master/src/libcore/lib.rs) though!

Thanks Simon - I've sent you a mail.

The debug build is a good call - I may have got somewhere with that: ``` (gdb) up 3 #3 0x00000000004f2bfb in Reporter::onLine (this=0x1e14f20, file="/checkout/src/libcore/lib.rs", lineNr=1, addr=93824992326304) at /data/mlt/kcov/src/reporter.cc:328 328...

OK, so this issue with the null reference is a bit of a red herring. :( The test I see at that commit is: ``` if (lines.size() >= lineNr -...

`skip-solibs` doesn't crash, but that's because of how Rust test binaries are built - by default everything is a library, and the test harness builds a minimal wrapper around it,...