Bug 1555038 - lcov seems entirely broken in F28
Summary: lcov seems entirely broken in F28
Keywords:
Status: CLOSED DUPLICATE of bug 1552042
Alias: None
Product: Fedora
Classification: Fedora
Component: lcov
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-13 20:37 UTC by Tom Lane
Modified: 2018-04-11 07:34 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-14 11:09:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


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