{"id":2856,"date":"2010-09-05T20:16:59","date_gmt":"2010-09-06T03:16:59","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=2856"},"modified":"2010-11-02T16:48:02","modified_gmt":"2010-11-02T23:48:02","slug":"using-gcovr-with-ffmpeg","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/using-gcovr-with-ffmpeg\/","title":{"rendered":"Using gcovr with FFmpeg"},"content":{"rendered":"

When I started investigating code coverage tools to analyze FFmpeg<\/a>, I knew there had to be an easier way to do what I was trying to do (obtain code coverage statistics on a macro level for the entire project). I was hoping there was a way to ask the GNU gcov tool to do this directly. John K informed me in the comments<\/a> of a tool called gcovr<\/a>. Like my tool from the previous post, gcovr is a Python script that aggregates data collected by gcov. gcovr proves to be a little more competent than my tool.<\/p>\n

Results<\/strong>
\nHere is the spreadsheet of results<\/a><\/strong>, reflecting FATE<\/a> code coverage as of this writing. All FFmpeg source files are on the same sheet this time, including header files, sorted by percent covered (ascending), then total lines (descending).<\/p>\n

Methodology<\/strong>
\nI wasn’t easily able to work with the default output from the gcovr tool. So I modified it into a tool called gcovr-csv which creates data that spreadsheets can digest more easily.<\/p>\n