Yegappan Lakshmanan wrote: > Just in case anyone is looking for getting the code coverage information > for Vim, I used the following steps to get this. > > 1. Modify src/Makefile and add the following two lines: > > CFLAGS=-g -O0 -fprofile-arcs -ftest-coverage > LDFLAGS=--coverage > > 2. Run configure and build Vim as usual. > 3. Run "make test" to run the unit tests. > 4. The code coverage information will be generated in the src/objects > directory. > 5. Use the following command to get the code coverage information for a > particular source file: > > $ cd src > $ gcov -o objects <filename.c> > > The code coverage information will be in the <filename.c>.gcov file.
Thanks, I'll add this in src/Makefile How does one clean up afterwards? -- A real patriot is the fellow who gets a parking ticket and rejoices that the system works. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
