From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: Sun, 11 Mar 2018 13:58:21 -0400
Message-ID: <30669.1520791101@sss.pgh.pa.us> (raw)
In-Reply-To: <30195.1520790475@sss.pgh.pa.us>
References: <30022.1520642188@sss.pgh.pa.us>
<d0eec0fd-bf3b-55da-f5de-4fa1c00ce400@2ndquadrant.com>
<CABUevEyydszbZJPF6iyjU45C+Kx4YSCa+KDZJkXNdjiGbE0Ojg@mail.gmail.com>
<30195.1520790475@sss.pgh.pa.us>
I wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> Is it specifically "lcov" we are considering here? If so, we are on version
>> 1.13, and there is no newer version packaged for debian or from what I can
>> tell even released?
> It could also be a compiler issue, I believe.
Actually, looking closer, it appears that lcov is just translating
gcov's textual output into HTML, so that the error is probably to
be blamed on gcc or gcov. And at least on RHEL, those come from
the same package:
$ rpm -qf /usr/bin/gcov
gcc-4.4.7-18.el6.x86_64
So if you're up2date on gcc, we might have material for a gcc bug report
here. I'll try to reproduce it on recent Fedora, and if so file something
at Red Hat.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-www@postgresql.org
Cc: tgl@sss.pgh.pa.us, magnus@hagander.net, peter.eisentraut@2ndquadrant.com, pgsql-www@lists.postgresql.org
Subject: Re: Bogus reports from coverage.postgresql.org
In-Reply-To: <30669.1520791101@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox