You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, drcov2lcov does not reflect how many times each line was executed in coverage.info it produces. Just 1 or zero. For real lcov files we get the execution counter for each line.
Is there any reason for such implementation? Would you consider fixing this?
The text was updated successfully, but these errors were encountered:
Determining whether a line was executed is easily gathered with almost zero overhead beyond DR's base overhead, as you can imagine from how DR operates: that requires only transformation-time actions (If you are not familiar with transformation time versus execution time, please see http://dynamorio.org/API_BT.html#sec_control_points). Adding counts adds non-negligible overhead as it requires execution-time actions.
If you would like to add counts, that makes sense as an optional feature controlled by a runtime option so those who do not need it do not pay the overhead cost. We would be happy to consult on how to do that and to review pull requests.
Currently, drcov2lcov does not reflect how many times each line was executed in coverage.info it produces. Just 1 or zero. For real lcov files we get the execution counter for each line.
Is there any reason for such implementation? Would you consider fixing this?
The text was updated successfully, but these errors were encountered: