|
From: Bryan M. <om...@br...> - 2006-08-04 20:37:47
|
Fellow Valgrinders, please check my small web page for the details: http://www.brainmurders.eclipse.co.uk/covergrind.html >From the web page: ------------------ Covergrind is a code coverage tool for the excellent Valgrind framework. Rather than having to link against strange libraries or compile in various support, Covergrind uses run time instrumentation in order to work out which parts of your source code are traversed. There have been comments made about how trivial it would be to use the Valgrind framework to construct such a tool but I wasn't able to find one so here is mine to share. ------------------ Basically does what it says - run your program with Covergrind and it will output a list of filenames and line number ranges in a simple man/machine readable format so you can check your code coverage. I am hoping to put a simple GUI together to read the output and colour source files accordingly but I haven't got there yet (I normally do low level and device driver stuff so go easy on me :P). The main advantage of this tool (beyond the standard Valgrind advantages of not having to mess around with your source code or build system) is that it is lightweight compared to Memcheck or Callgrind, mainly because it is only providing a single tiny set of functionality. A secondary advantage is that if you are set up to Valgrind your code, you are also set up to Covergrind it... Only tested on x86_64 so far but may well work on other platforms. Feel free to give it a spin and post your experiences to the list. As ever, I welcome your comments and bug reports. Bryan "Brain Murders" Meredith ps. Julian/Nick - happy to change the name if you are uncomfortable with it for ANY reason. |