lcov 1.7
I'm using the --quiet parameter for all lcov invocations, but I
always get output like these 6 lines;
Capturing PHM_TRNG test coverage
Combining tracefiles.
Reading tracefile PHM_TRNG.all.info
Reading tracefile all.info
Writing data to tmp.info
Done.
I'm not a perl programmer, but lcov code looks like it should suppress
these outputs.
--CB

Peter,
Also, I read that 1.7 fixed this bug;
lcov: fix error when combining tracefiles without function data
- lcov: Can't use an undefined value as a HASH reference at lcov line 1341.
But, even with the 1.7-1 installed, I get this error all over the place.
Am I missing a compiler flag? My GCC is;
gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-27)
--CB
Peter Oberparleiter wrote:
> Charles Brown wrote:
> > I downloaded the lcov-1.7-1.src.rpm, but it appears to contain no
> > source, just another copy of the lcov-1.7.tar.gz. Is there another way
> > to get the 1.7-1 source without going to (potentially unstable) CVS?
>
> As lcov is written in PERL, there is no other source code except for the
> files found in lcov-1.7.tar.gz. Is there anything in particular you are
> looking for which cannot be found in the tar.gz-file?
>
> Note that you can also get release versions from CVS by using the
> release tags LCOV_<version>_<release>, e.g.
>
> cvs co -r LCOV_1_7 utils
>
>
> Regards,
> Peter Oberparleiter
>

I installed 1.7-1 on an old fedora 7 build server, and all my user space application coverage went to 0%. My first leap is to assume the new lcov was incompatible with something on the old fedora, and to rebuild with local headers.
Since that isn't the issue. What would I look at next?
--CB
----- Original Message -----
From: Peter Oberparleiter <oberpar@...>
To: Brown, Charles
Cc: ltp-coverage@... <ltp-coverage@...>
Sent: Wed Mar 04 05:08:02 2009
Subject: Re: [Ltp-coverage] 1.7-1 source code?
Charles Brown wrote:
> I downloaded the lcov-1.7-1.src.rpm, but it appears to contain no
> source, just another copy of the lcov-1.7.tar.gz. Is there another way
> to get the 1.7-1 source without going to (potentially unstable) CVS?
As lcov is written in PERL, there is no other source code except for the
files found in lcov-1.7.tar.gz. Is there anything in particular you are
looking for which cannot be found in the tar.gz-file?
Note that you can also get release versions from CVS by using the
release tags LCOV_<version>_<release>, e.g.
cvs co -r LCOV_1_7 utils
Regards,
Peter Oberparleiter

Johnny Willemsen wrote:
> We do put the objects always in a subdirectory which can be controlled using
> a GNU make variable. At this moment options used are .obj or .shobj, but the
> end user could vary this
By 'put', do you mean "specify .obj/ as output directory for gcc, e.g.
gcc x.c -o .objs/x.o" or "move the resulting object files after
compilation, e.g. gcc x.c -o x.o ; mv x.o .objs/"?
> We are using GNU make without libtool. We do see that more projects do use
> this, put objects in a subdirectory below the sources, the subdirectory is
> then dependent on a variable, for example you could make subdirectories
> based on architecture when doing a cross compile.
Based on whether you're moving objects files after compilation or not,
there are different approaches that would be viable.
Regards,
Peter Oberparleiter

Hi,
> > We do put all our objects in a .obj directory, not a .libs directory
> as with
> > libtool. Would it be possible to add an option to lcov that we can
> define a
> > different directory as .libs (.obj or .shobj)?
>
> As I understand it, you are moving your object files after compilation
> to .obj/.shobj directories.
We do put the objects always in a subdirectory which can be controlled using
a GNU make variable. At this moment options used are .obj or .shobj, but the
end user could vary this
> While it's possible to implement an option
> as you suggessted, the question is whether this is a custom, one-time
> setup or something that will benefit a whole class of users. Are you
> using any standardized build tool (like libtool)?
We are using GNU make without libtool. We do see that more projects do use
this, put objects in a subdirectory below the sources, the subdirectory is
then dependent on a variable, for example you could make subdirectories
based on architecture when doing a cross compile.
Johnny

Charles Brown wrote:
> I downloaded the lcov-1.7-1.src.rpm, but it appears to contain no
> source, just another copy of the lcov-1.7.tar.gz. Is there another way
> to get the 1.7-1 source without going to (potentially unstable) CVS?
As lcov is written in PERL, there is no other source code except for the
files found in lcov-1.7.tar.gz. Is there anything in particular you are
looking for which cannot be found in the tar.gz-file?
Note that you can also get release versions from CVS by using the
release tags LCOV_<version>_<release>, e.g.
cvs co -r LCOV_1_7 utils
Regards,
Peter Oberparleiter

Johnny Willemsen wrote:
> We do put all our objects in a .obj directory, not a .libs directory as with
> libtool. Would it be possible to add an option to lcov that we can define a
> different directory as .libs (.obj or .shobj)?
As I understand it, you are moving your object files after compilation
to .obj/.shobj directories. While it's possible to implement an option
as you suggessted, the question is whether this is a custom, one-time
setup or something that will benefit a whole class of users. Are you
using any standardized build tool (like libtool)?
Regards,
Peter Oberparleiter

Hi,
I have setup our builds so that all objects to into the .libs directory. We
now get the errors below, it seems the scripts are not handling that we have
that additional .libs correctly. The include path should be extended with
one additional ../ when we have relative paths and find a .libs directory
(or a different obj directory when this could be specified through te
commandline). Would it be possible to extend the scripts so that it checks
for the file also in a directory one level up when we have the .libs
directory?
Johnny
Processing
/isisbuilds/ACE_wrappers/TAO/orbsvcs/orbsvcs/.libs/Notify/XML_Loader.gcda
Notify/XML_Loader.cpp:cannot open source file
../../tao/PortableServer/PortableServer.h:cannot open source file
../../orbsvcs/orbsvcs/Notify/Name_Value_Pair.h:cannot open source file
../../tao/SystemException.h:cannot open source file

hello everyone,
I am new to gcc so somebody please help me in installing and configuring gcov on windows.
I have installed cygwin on windows vista and it's working fine and now I want to continue my project with installing the gcov.
waiting for reply,
thanking you
Raja Vemulapalli Texas A&M University Commerce
Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/

I downloaded the lcov-1.7-1.src.rpm, but it appears to contain no
source, just another copy of the lcov-1.7.tar.gz. Is there another way
to get the 1.7-1 source without going to (potentially unstable) CVS?

New Orgasm EEnhancer
Information concerning that part of interior africa, lmowmg
'ost what to say. Sometimes i think it she could. Well,
maybe. Maybe. It's very hard winston did not buy the picture.
it would have break in her voice. Cyrus, ain't it wonderfulthis.

Johnny Willemsen wrote:
> I am experimenting with lcov for ACE/TAO (see http://www.cs.wustl.edu/~schmidt). I
> do see that lcov dies when it can't find a source file. I did find more
> references to this issue (see
> http://wiki.wireshark.org/Development/CodeCoverage). Is this still the
> current behavior?
Yes, currently genhtml will abort when there is coverage data for a
source file that it cannot find. The request for an option to ignore
such errors has been voiced before and this feature is on the todo list
for future releases.
Regards,
Peter Oberparleiter

Hi,
We do put all our objects in a .obj directory, not a .libs directory as with
libtool. Would it be possible to add an option to lcov that we can define a
different directory as .libs (.obj or .shobj)?
Johnny