search for: genhtml

...and recompile. This time vmac.gcda file wont appear in /proc/xen/gcov/crypto HOWTO Test using lcov 1. install lcov from repo # sudo apt-get install lcov 2. vi /etc/lcovrc Change line: lcov_gcov_dir = /proc/gcov to lcov_gcov_dir = /proc/xen/gcov 3. # cd /tmp; lcov -c -o kernel.info 4. # genhtml kernel.info 5, # firefox index.html lcov README and screenshot is attached. HTH Note: For any other detail required please CC me to parkash.tej@gmail.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-deve...

...and recompile. This time vmac.gcda file wont appear in /proc/xen/gcov/crypto HOWTO Test using lcov 1. install lcov from repo # sudo apt-get install lcov 2. vi /etc/lcovrc Change line: lcov_gcov_dir = /proc/gcov to lcov_gcov_dir = /proc/xen/gcov 3. # cd /tmp; lcov -c -o kernel.info 4. # genhtml kernel.info 5, # firefox index.html lcov README and screenshot is attached. HTH Note: For any other detail required please CC me to parkash.tej@gmail.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-deve...

...subpage on the Crossbow projects. These two articles are the first of a number of online articles on Crossbow that I''ll be creating on behalf of the Crossbow iteam. The article uses Wikipedia''s recommended, encyclopedic style. It is essentially a survey. The attached file is in GenHTML. Some of the links aren''t live but they will be when I redo by hand the article in Wikipedia''s Wiki markup. Anyway, I apologize for the generic, vendor-neutral nature of the first article. And I welcome contributions, even before this article gets posted on Wikipedia. - Stephani...

...ch was not. I used the approach from the next article to do that: http://logan.tw/posts/2015/04/28/check-code-coverage-with-clang-and-lcov/#create-a-wrapper-script-for-lcov In short, it is based on using -fprofile-arcs -ftest-coverage clang flags and then generating the HTML report using lcov and genhtml tools. The results are actually not that bad (I expected we would have much more issues, but glad to see we seem don't :) Coverage screenshot: https://drive.google.com/file/d/1rjFdMA0HOjvz4vw_nDttv_dlbMiNYiaw/view We have few problematic places, but generally seems we cover the most of the co...

...used the approach from the next article to do that: > http://logan.tw/posts/2015/04/28/check-code-coverage-with-clang-and-lcov/#create-a-wrapper-script-for-lcov > > In short, it is based on using -fprofile-arcs -ftest-coverage clang flags and then generating the HTML report using lcov and genhtml tools. > > The results are actually not that bad (I expected we would have much more issues, but glad to see we seem don't :) > Coverage screenshot: > https://drive.google.com/file/d/1rjFdMA0HOjvz4vw_nDttv_dlbMiNYiaw/view > > We have few problematic places, but generally seems...

...ot;hello1" ./simple "hello2" ./simple "hello3" ./simple "hello4" ./simple "hello5" ./simple "hello6" ./simple "hello7" ./simple "hello8" lcov --rc lcov_branch_coverage=1 --capture --directory . --output-file simple.lcov.info genhtml simple.lcov.info --function-coverage --branch-coverage --output-directory lcov_out/ gcov -b -c simple.gcno Both gcov and lcov will give a 100% branch coverage report: [image: cov1.png] [image: cov2.png] My questions: - What's the "*official*" evaluation formula on branch cove...

Hi, Alan Really very excited to receive your email and sorry to be slow replying, it has been exceptionally busy over the last few days ;( Your explanation made the problem clear to me. So gcov branch coverage should be called condition coverage and clang region coverage is branch coverage in fact(also known as *decision/C1*), right? And llvm/clang will support all the following coverage