Idenmill, Ethan wrote:
> According to the changelog for November, 2007, there was a fix for the "ERROR: reading string" problem in lcov. Nevertheless, I am using lcov 1.61-1, and I am still seeing this show up. Was this fix not incorporated into 1.61-1? Where should I start looking to try to fix this problem? I just started working with lcov.
Assuming you're still looking for a solution to the problem you
described I will need more information. For once, try to reproduce the
problem with the latest CVS version of lcov (see
http://ltp.sf.net/coverage/lcov.php for instructions on how to obtain
the CVS version). If that doesn't work, please provide the .gcno file
that causes the problem.