Bug 377 - --lcov-report not working fully
: --lcov-report not working fully
Status: RESOLVED FIXED
: ns-3
general
: ns-3-dev
: All All
: P3 normal
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-10-10 17:34 EDT by
Modified: 2009-04-24 07:39 EDT (History)


Attachments
Avoids reading of garbage data (449 bytes, patch)
2009-04-23 11:38 EDT, Faker Moatamri
Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-10-10 17:34:22 EDT
./waf --lcov-report works for the unit tests, but not for examples or
regression.

How to reproduce:
./waf configure --enable-gcov
./waf
./waf check
./waf --lcov-report 

(works so far, but then)
./waf --regression
./waf --lcov-report
exits with this error:

./waf --lcov-report
Entering directory `/home/tomh/hg/ns-3-dev/build'
Compilation finished successfully 
Capturing coverage data from .
Found gcov version: 4.2.3
Scanning . for .gcda files ...
Found 253 data files in .
Processing ./debug-gcov/examples/csma-multicast_12.gcda
ERROR: reading string
------- Comment #1 From 2008-10-10 17:37:09 EDT -------
A note on this configuration:

for ns-3, there is a specialized version of lcov-1.4 that resides in utils/lcov
directory.  The current stable version is lcov-1.6.  Note that any attempt to
migrate lcov-1.4 to lcov-1.6 in utils/lcov should preserve the existing patch
(plus whatever is needed to make it work on regression).
------- Comment #2 From 2008-10-23 00:33:33 EDT -------
agreed on 10/22 to try to fix this for 3.3 release (non-blocker)
------- Comment #3 From 2008-10-24 09:13:06 EDT -------
(In reply to comment #1)
> A note on this configuration:
> 
> for ns-3, there is a specialized version of lcov-1.4 that resides in utils/lcov
> directory.  The current stable version is lcov-1.6.  Note that any attempt to
> migrate lcov-1.4 to lcov-1.6 in utils/lcov should preserve the existing patch
> (plus whatever is needed to make it work on regression).

The same error happens with lcov 1.6
------- Comment #4 From 2008-10-24 09:37:35 EDT -------
a simple fix is to ignore the error from the wscript and proceed with html
generation anyway. 
------- Comment #5 From 2009-04-23 11:38:31 EDT -------
Created an attachment (id=426) [details]
Avoids reading of garbage data
------- Comment #6 From 2009-04-24 07:39:10 EDT -------
changeset: 412842631b1d