Bug 1555038

Summary: lcov seems entirely broken in F28
Product: [Fedora] Fedora Reporter: Tom Lane <tgl>
Component: lcovAssignee: Daniel Berrangé <berrange>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: berrange, mcepl, mcepl, roland
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-14 11:09:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom Lane 2018-03-13 20:37:27 UTC 
Description of problem:
lcov seems unable to read the .gcno files made by F28's version of gcc.

Version-Release number of selected component (if applicable):
lcov-1.13-2.fc28.noarch
also
gcc-8.0.1-0.16.fc28.x86_64

How reproducible:
100%

Steps to Reproduce:
1. try to lcov something

Actual results:
lots of failures like
geninfo: WARNING: /home/tgl/pgsql/src/backend/storage/lmgr/s_lock.gcno: Overlong record at end of file!
geninfo: WARNING: /home/tgl/pgsql/src/backend/storage/lmgr/predicate.gcno: Overlong record at end of file!
geninfo: ERROR: /home/tgl/pgsql/src/backend/storage/lmgr/lwlocknames.gcno: reached unexpected end of file


Expected results:
success

Additional info:
I can give you a recipe for reproducing this with the Postgres sources, if by some chance you don't see it on anything else you might try.  But it doesn't look to me like this is working at all.

Looking at lcov upstream commit log says they added "support for gcc 8" last week, so maybe you need to prod them to make a release, or absorb the changes as a temporary patch.
Comment 1 Daniel Berrangé 2018-03-14 11:09:16 UTC 
Already reported in bug 1552042, but I forgot to build into f28 dist.

*** This bug has been marked as a duplicate of bug 1552042 ***