zachriggle/covpare

Simple tool for comparing gcov/llvm-cov output between runs

About me:

• ✨ Washed up hacker, Ḃṵsṫĭȼầṫoṝ, and Bourbon aficionado
• 🌍 Austin, TX
• 🛠 Open Source contributor
  • pwntools exploit development library (maintainer)
  • pwndbg reverse engineering with GDB made simple (maintainer)
  • gatekeeper attack-defense CTF mitigations (author)
• 💼  Apple Security Engineering & Research (work with me)
• 📫 Contact me on: twitter · linkedin · discord

covpare's Issues

gives all kinds of json debug output that is not requested

folkert@msi:~/Projects/git/covpare$ python compare.py bla1 bla2 --line-diff | less
...
t1/allocator.h:280 | 0 0 | _GLIBCXX_END_NAMESPACE_VERSION
t1/allocator.h:281 | 0 0 | } // namespace std
t1/allocator.h:282 | 0 0 |
t1/allocator.h:283 | 0 0 | #endif
{u'_id': ObjectId('5e3056fcca62807fff6fe1e8'),
u'blocks': 100,
u'calls': 374,
u'filename': u't1/basic_string.h',
u'lines': [{u'blocks': [],
u'branches': [],
u'hits': 1.0,
u'lineno': 156,
...

Processing lcov output en masse

As an alternative to using gcov repeatedly for every source dir / file in our project, we run coverage reports using a combination of lcov and genhtml. In order to produce reports via Cobertura (or simple HTML reports), we use the gcovr python utility.

We have a use case for which the covpare utility but it would be helpful if we could get some direction on how best to utilize the info file that is generated by lcov.