Gcov - Revision history

Jpye: /* ggcov */

2026-02-08T09:16:53Z

ggcov

← Older revision		Revision as of 09:16, 8 February 2026
Line 82:		Line 82:
	To get fresh tallies of covered code you might need to remove the coverage data, eg		To get fresh tallies of covered code you might need to remove the coverage data, eg

	<source lang=sh>		<source lang=shellscript>
	find . -name "*.gcda" \| xargs rm		find . -name "*.gcda" \| xargs rm
	</source>		</source>

	[[Category:Development]]		[[Category:Development]]

2026-02-08T09:16:41Z

ggcov

← Older revision		Revision as of 09:16, 8 February 2026
Line 66:		Line 66:
	Currently, ggcov gets all confused if there aren't <tt>.o</tt> files to match the <tt>.gcno</tt> files produced by the <tt>--coverage</tt> instrumentation in GCC. You can quickly create at least the need .o files by copying all the .os files that SCons produces to corresponding .o files:		Currently, ggcov gets all confused if there aren't <tt>.o</tt> files to match the <tt>.gcno</tt> files produced by the <tt>--coverage</tt> instrumentation in GCC. You can quickly create at least the need .o files by copying all the .os files that SCons produces to corresponding .o files:

	<source lang=sh>		<source lang=shellscript>
	find . -name "*.os" \| xargs rename 's/\.os$/\.o/'		find . -name "*.os" \| xargs rename 's/\.os$/\.o/'
	</source>		</source>

2026-02-08T09:16:32Z

lcov

← Older revision		Revision as of 09:16, 8 February 2026
Line 30:		Line 30:
	To run lcov with ASCEND, try the following:		To run lcov with ASCEND, try the following:

	<source lang=sh>		<source lang=shellscript>
	#!/bin/bash		#!/bin/bash

2026-02-08T09:16:23Z

← Older revision		Revision as of 09:16, 8 February 2026
Line 3:		Line 3:
	To get coverage information in plaintext form, for a single code file, you can use the <tt>gcov</tt> command, eg		To get coverage information in plaintext form, for a single code file, you can use the <tt>gcov</tt> command, eg

	<source lang=sh>		<source lang=shellscript>
	# run all this from the top-level working directory		# run all this from the top-level working directory
	cd ~/ascend		cd ~/ascend

2017-09-17T04:40:54Z

lcov

← Older revision		Revision as of 04:40, 17 September 2017
Line 24:		Line 24:
	== lcov ==		== lcov ==

	The [http://ltp.sourceforge.net/coverage/lcov.php lcov] tool can be used to produce nice, easy-to-read coverage reports from our CUnit test suite (and probably more). To run lcov with ASCEND, try the following:		The [http://ltp.sourceforge.net/coverage/lcov.php lcov] tool can be used to produce nice, easy-to-read coverage reports from our CUnit test suite (and probably more).

			'''Note:''' we found that the version of LCOV available in the Ubuntu repositories was not functional, and the newer code from <tt>git clone https://github.com/linux-test-project/lcov.git</tt> needed to be used. It can be built and installed using <tt>sudo make install</tt>, which will install it to <tt>/usr/local/bin/lcov</tt>.

			To run lcov with ASCEND, try the following:

	<source lang=sh>		<source lang=sh>

2017-07-10T15:53:10Z

← Older revision		Revision as of 15:53, 10 July 2017
Line 49:		Line 49:
	Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.		Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.

	The above approach has been implemented in a Python script {{srcbranch\|relerrorlist\|test/test-cov.py}} which be run to produce full coverage reports for the {{CUnit}} test suite in ASCEND. So far we don't have any coverage testing from the Python or C++ parts.		The above approach has been implemented in a Python script {{srcbranch\|relerrorlist\|test/test-cov.py}} which be run to produce full coverage reports for the [[CUnit]] test suite in ASCEND. So far we don't have any coverage testing from the Python or C++ parts.

	== ggcov ==		== ggcov ==

2017-05-07T08:19:39Z

← Older revision		Revision as of 08:19, 7 May 2017
Line 49:		Line 49:
	Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.		Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.

	The above approach has been implemented in a Python script {{~~src~~\|test/test-cov.py}} which be run to produce full coverage reports for the {{CUnit}} test suite in ASCEND. So far we don't have any coverage testing from the Python or C++ parts.		The above approach has been implemented in a Python script {{srcbranch\|relerrorlist\|test/test-cov.py}} which be run to produce full coverage reports for the {{CUnit}} test suite in ASCEND. So far we don't have any coverage testing from the Python or C++ parts.

	== ggcov ==		== ggcov ==

2017-05-07T08:19:08Z

lcov

← Older revision		Revision as of 08:19, 7 May 2017
Line 48:		Line 48:

	Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.		Note that the command <tt>$LCOV -r mycov-tot.info "stdout" -o mycov-tot2.info</tt> is required, because of the way the {{src\|ascend/compiler/scanner.l}} file is compiled. In the gcov output it is shown with a source-code filename of <stdout>, which is incorrect/false.

			The above approach has been implemented in a Python script {{src\|test/test-cov.py}} which be run to produce full coverage reports for the {{CUnit}} test suite in ASCEND. So far we don't have any coverage testing from the Python or C++ parts.

	== ggcov ==		== ggcov ==

2017-05-06T09:38:26Z

@@ Line 21: / Line 21: @@
 * <tt>gcov</tt> shows results one file at a time. Tools like <tt>[http://ggcov.sf.net/ ggcov]</tt>, <tt>[http://linux.die.net/man/1/lcov lcov]</tt>, <tt>[https://software.sandia.gov/trac/fast/wiki/gcovr gcovr]</tt> can give some aggregated coveraged data, create GUI/HTML output, and convert to 'cobertura' output format for use with other tools.
 * See also gprof if you want information about time spent in different functions.
 == ggcov ==

2012-10-02T12:52:32Z

← Older revision		Revision as of 12:52, 2 October 2012
Line 13:		Line 13:
	gcov -p ascend/compiler/mergeinst.c --object-directory ascend/compiler		gcov -p ascend/compiler/mergeinst.c --object-directory ascend/compiler
	# view the results		# view the results
	vim ascend#compiler#merginst.c.gcov		vim ascend\#compiler\#merginst.c.gcov
	</source>		</source>