| Age | Commit message (Collapse) | Author |
|---|
|
Noticed by pyflakes. I've no idea what sort of errors it could've
caused at runtime.
|
|
* Ask gcov to resolve what source files a gcno file represents.
* This also covers issues with multiple gcno files for the same
source file, as would be the case if a source file is built
into multiple executables/libraries.
|
|
No gcno file indicates that the the source was not built with
code coverage. If the gcno file exists but predates the source
file, then probably not rebuilt since last change.
|
|
gcov needs to be run in the same directory as gcc was run in order
to find the source files correctly. We use gcov with --no-output to
report which directory this is for given gcno files.
|
|
|
|
|
|
|
|
|
|
|
|
|
