Running gcov when executable has command line input options

jasper77 · 03-03-2011, 01:56 PM

I have an executable with input options, like so:

Code:

./executable -n 42 -s 42

I've added gcov to the makefiles (compiling with --coverage, -fprofile-arcs, and -ftest-coverage, and linking with -lgcov). It builds fine and creates executable.gcno.

When I try to run gcov, gcov things the options belong to it:

Code:

$ gcov ./executable -n 42 -s 42
gcov: invalid option -- 's'
Usage: gcov [OPTION]... SOURCEFILE...

When I use quotes this happens:

Code:

$ gcov './executable -n 42 -s 42'
executable -n 42 -s 42.gcno:cannot open graph file

The command line options must remain. How can I get gcov to generate the same .gcno file it later looks for?

jasper77 · 03-03-2011, 02:08 PM

Answering my own question... almost...

Explicitly tell gcov the name of the object file with a flag as follows. But then this happens:

Code:

$ gcov --object-file executable './executable -n 42 -s 42'
executable.gcda:cannot open data file, assuming not executed

... and then I get a bunch of output telling me 0.00% of lines in each file were executed.
When I list the directory, there are no .gcda files.

dwhitney67 · 03-03-2011, 04:55 PM

It's been years since I have used gcov, but I believe you are almost correct with your approach. The only issue you are missing is producing the results.

So first, compile/link your program as you have been doing. Then second, run your program with the command-line args. Then finally, run gcov against the executable.gcda file.

For example:

Code:

gcc --coverage -fprofile-arcs -ftest-coverage MySource.c -o executable -lgcov   # Step 1

./executable -n 42 -s 42   # Step 2

gcov executable.gcda   # Step 3

You should then have one or more .gcov files that you can examine. The one that will probably interest you the most is the one named MySource.c.gcov.

If you want your executable to run a different path, then re-run it (step 2), and then re-run step 3. Then re-examine the .gcov file(s).