xaizek

> I have the same problem, probably more people have this problem. I don't think the problem of this issue has been identified, you might have the same symptom though....

`gcov --json-format` provides ranges for functions (this is from `man gcov`): ``` Each function has the following form: { "blocks": , "blocks_executed": , "demangled_name": ", "end_column": , "end_line": , "execution_count":...

As I remember, codecov scripts upload coverage information to their servers for processing. So you want to consult their documentation for some kind of filtering and if that's not present...

Fixing lcov won't fix codecov.

Both codecov and lcov use data from gcov. There is no need to use lcov for codecov, it will only make things harder.

I think [bug#82702](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82702) was about this issue with intermediate format (although it says that only one file was produced prior to GCC 6, my gcc 5.5.0 creates multiple files as...

> @xaizek you are seeing one gcov file per .c file on 5.5.0? Yes, because that commit was backported: https://github.com/gcc-mirror/gcc/commit/ac470b78b552247be1d42fae5539f6ab18b12a97 So some earlier version of GCC 5 must have worked...

> If so: then, unless you have done a bit of additional infrastructure work, your issue is that there is no interlock between the different executable instances when they go...

NFS seems to support locking, however [man page](https://man7.org/linux/man-pages/man2/fcntl.2.html) specifies that locks might misbehave on network issues or administrative changes on remote machine. Other file systems might differ in support and...

Помню на подкасте Гор Нишанов прямо гордился тем, что в отличии от C они запретили инициализировать поля в неправильном порядке или не в полном объёме. Но он не объяснял, что...