| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bogus reports from coverage.postgresql.org |
| Date: | 2018-03-11 17:58:21 |
| Message-ID: | 30669.1520791101@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
I wrote:
> Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-03-11 18:02:29 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Tom Lane | 2018-03-11 17:47:55 | Re: Bogus reports from coverage.postgresql.org |