[Gluster-infra] [Bug 1757804] Code coverage - call frequency is wrong

bugzilla at redhat.com bugzilla at redhat.com
Thu Oct 3 10:49:05 UTC 2019


--- Comment #4 from M. Scherer <mscherer at redhat.com> ---
so maybe the problem is that since the code is using spinlock sometime (but not
always), and spinlock by nature would be a empty loop, then it might explain
for that specific case why it do run more often than the rest of the function.
Since that's a macro expanded to multiline code, I guess lcov/gcov might get
confused by the fact that some part of the code is running more than the
others, or something like that. There is a option on gcov for that (-a), but
not in lcov. 

But again, that would matter only if we were looking at doing something with
that precise info, no ?

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Gluster-infra mailing list