scons-tool-gcccov
Support for gcc code coverage features. Note, this is not a tool for running gcov program.
Overview
gcc (and clang) is able to generate coverage info for gcov tool. You can use gcov to test code coverage in your programs. It helps discover where your optimization efforts will best affect your code.
gcov uses two files for profiling, see gcov files. The names of these files are derived from the original object file by substituting the file suffix with either .gcno, or .gcda. The .gcno notes file is generated when the source file is compiled. The .gcda count data file is generated when a program containing object files is executed. A separate .gcda file is created for each object file.
The purpose of scons-tool-gcccov is to help to incorporate the above gcov files into project’s dependency tree. Thanks to this, builders that depend on coverage data (for example gcov report builders or test runners) may be executed at right moments. This also helps to clean-up coverage data when the project gets cleaned up.
Installation
There are few ways to install this tool for your project.
From pypi
This method may be preferable if you build your project under a virtualenv. To add gcccov tool from pypi, type (within your wirtualenv):
pip install scons-tool-loader scons-tool-gcccov
or, if your project uses pipenv:
pipenv install --dev scons-tool-loader scons-tool-gcccov
Alternatively, you may add this to your Pipfile
[dev-packages]
scons-tool-loader = "*"
scons-tool-gcccov = "*"
The tool will be installed as a namespaced package sconstool.gcccov in project’s virtual environment. You may further use scons-tool-loader to load the tool.
As a git submodule
Create new git repository:
mkdir /tmp/prj && cd /tmp/prj touch README.rst git initAdd the scons-tool-gcccov as a submodule:
git submodule add git://github.com/ptomulik/scons-tool-gcccov.git site_scons/site_tools/gcccovFor python 2.x create __init__.py in site_tools directory:
touch site_scons/site_tools/__init__.pythis will allow to directly import site_tools.gcccov (this may be required by other tools).
Other projects
Download and copy this source tree to site_scons/site_tools/gcccov/ subdirectory of your project:
mkdir -p site_scons/site_tools/gcccov && \ (cd site_scons/site_tools/gcccov && \ curl -L https://github.com/ptomulik/scons-tool-gcccov/tarball/master | \ tar --strip-components=1 -xz)
Usage
Integrating with cxxtest
In this example we create a simple test runner using cxxtest suite. To drive everything from SCons, we’ll use a scons-tool-cxxtest tool derived from the original SCons tool available in cxxtest repository.
Install cxxtest framework:
sudo apt-get install cxxtestCreate new git repository:
mkdir /tmp/prj && cd /tmp/prj touch README.rst git initAdd scons-tool-gcccov as submodule:
git submodule add git://github.com/ptomulik/scons-tool-gcccov.git site_scons/site_tools/gcccovAdd scons-tool-cxxtest tool as submodule:
git submodule add git://github.com/ptomulik/scons-tool-cxxtest.git site_scons/site_tools/cxxtestCreate source file src/bar.cpp:
// src/bar.cpp int bar() { return 0; }Create test file src/test.t.h
// src/test.t.h #include <cxxtest/TestSuite.h> extern int bar(); class BarTestSuite1 : public CxxTest::TestSuite { public: void testBar(void) { TS_ASSERT_EQUALS(bar(), 0); } };Write the top level SConstruct file:
# SConstruct import os env = Environment(ENV = os.environ, tools = ['default', 'cxxtest', 'gcccov']) # Generate correct dependencies of `*.gcno' and `*.gcda' files on object # files being built from now on. env.GCovInjectObjectEmitters() env.Replace(CCFLAGS = ['-g', '-O0', '--coverage'], LINKFLAGS = ['--coverage']) SConscript('src/SConscript', variant_dir = 'build', duplicate = 0, exports = [ 'env' ])Write src/SConscript:
# src/SConscript Import(['env']) bar = env.SharedLibrary(['bar'], ['bar.cpp']) env.CxxTest('test.t.h', LIBS = bar)Try it out:
ptomulik@barakus:$ LD_LIBRARY_PATH=build scons -Q check Loading CxxTest tool... /usr/bin/python /usr/bin/cxxtestgen --runner=ErrorPrinter -o build/test.cpp src/test.t.h g++ -o build/test.o -c -g -O0 --coverage -I. build/test.cpp g++ -o build/bar.os -c -g -O0 --coverage -fPIC src/bar.cpp g++ -o build/libbar.so --coverage -shared build/bar.os g++ -o build/test --coverage build/test.o -Lbuild -Lsrc -lbar /tmp/prj/build/test Running cxxtest tests (1 test).OK!Check the gcov files created:
ptomulik@barakus:$ ls build/*.gc* build/bar.gcda build/bar.gcno build/test.gcda build/test.gcnoCleanup project:
ptomulik@barakus:$ scons -Q -c Loading CxxTest tool... Removed build/bar.os Removed build/bar.gcno Removed build/bar.gcda Removed build/libbar.so Removed build/test.cpp Removed build/test.o Removed build/test.gcno Removed build/test.gcda Removed build/testAs you see, all the generated gcov side effects are cleaned up as expected.
Finding out *.gcda files generated by a program run
If you need a list of *.gcda files generated when a program built with SCons is executed, you may use GCovFindGcdaNodes:
prog = env.Program('foo.c') gcda = env.GCovFindGcdaNodes(prog[0])
This method is kinda dangerous and may break some builds. It internally scans for dependencies, and this is done at the time the SConscript file is processed. This may cause a problem with .sconsing file being written to wrong directory. More details are given in this thread.
As a conclusion I would say, that you should not use it in normal workflow. However, it may be handy for development, code maintenance and such. For these purposes I would suggest to add special CLI options or targets to your SCons script, to use it only when explicitly requested.
Module description
The scons-tool-gcccov tool provides three methods:
env.GCovInjectObjectEmitters(**overrides),
env.GCovFindGcdaNodes(root),
env.GCovGcdaGenerator(target, target_factory=_null, **overrides).
The first method, GCovInjectObjectEmitters is the only you’ll need in most projects. It injects special emitter to builders which create C/C++ object files such that their corresponding *.gcno and *.gcda files get added to dependency tree. The method should be invoked somewhere on the top of your SConstruct, before you specify first C/C++ file to be compiled. For example, this is incorrect:
# SConstruct env.Program('foo') env.GCovInjectObjectEmitters()
and this is correct:
# SConstruct env.GCovInjectObjectEmitters() env.Program('foo')
The remaining two methods should not be used in normal workflow. The GCovFindGcdaNodes determines what *.gcda files would be generated when running certain program(s) built with SCons. The GCovGcdaGenerator(alias) tells SCons that alias target generates these *.gcda files as a side effect (the alias should run a program/test runner and should have the program in its dependencies). The method should not be used currently, however, as it may break some builds, see this thread. Currently it’s here only for experiments.
Construction variables
The tool uses construction variables listed in the table below:
Option |
Description |
|---|---|
GCCCOV_DISABLE |
Disable gcccov functionality. |
GCCCOV_EXCLUDE |
Files (*.gcno, *.gcda, objects, etc.) to be excluded from processing. |
GCCCOV_GCDA_SUFFIX |
Suffix for *.gcda files used by gcov dependency machinery. |
GCCCOV_GCNO_SUFFIX |
Suffix for *.gcno files used by gcov dependency machinery. |
GCCCOV_MAX_RECURSION |
Maximum recursion depth allowed when searching for *.gcda nodes. |
GCCCOV_NOCLEAN |
List of gcov files which shouldn’t be Cleaned up. |
GCCCOV_NOIGNORE |
List of gcov files which shouldn’t be Ignored from main target. |
GCCCOV_RUNTEST_FACTORY |
Factory used to build runtest target (defaults to env.ans.Alias) |
GCCCOV_RUNTEST_TARGETS |
List of targets (usually aliases) that run test runners. |
GCCCOV_SOURCE_SUFFIXES |
List of source file suffixes for which dependency injector should be enabled. |
GENERATING DOCUMENTATION
API DOCUMENTATION
You need few prerequisites to generate API documentation:
Install them with
sudo apt-get install python-epydoc python-docutils python-pygments
The API documentation may be generated with:
scons api-doc
The resultant html files get written to build/doc/api directory.
LICENSE
Copyright (c) 2014-2020 by Paweł Tomulik <ptomulik@meil.pw.edu.pl>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
Metadata
Release files for scons-tool-gcccov 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scons-tool-gcccov-0.2.0.tar.gz | 16.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scons_tool_gcccov-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.7 kB
Release files / scons-tool-gcccov-0.2.0.tar.gz
| Download URL | scons-tool-gcccov-0.2.0.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5b477af87624013185ed22b3f357d002e6adba12401fe097d7f42a0b1086e1a
|
|
BLAKE2b-256 checksum How to use checksums |
c10ed7c2c0dfa19542a1f823b3c35b18def8b399c38cbdccf581353a1201c282
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Release files / scons_tool_gcccov-0.2.0-py3-none-any.whl
| Download URL | scons_tool_gcccov-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c016245910562db0b5d8309c4855444f96ff731fb6a71c09854292a1b999456b
|
|
BLAKE2b-256 checksum How to use checksums |
51053783c841f2db8d6c24eb24dd66eb6d051f68a166ff18ffe1caccc67fa399
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for scons-tool-gcccov 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.