gcov support for glibc

gcov support for glibc

[Palleti, Avinash Reddy]

Hi,

We are trying to get coverage analysis for glibc test cases, we tried below command to enable gcov support while building glibc.

CFLAGS="-ftest-coverage -fprofile-arcs -O2 -U_FORTIFY_SOURCE" CXXFLAGS="-ftest-coverage -fprofile-arcs" LD_FLAGS="-fprofile-arcs" ../configure --prefix=/opt/ --disable-werror  libc_cv_ctors_header=yes libc_cv_c_cleanup=yes

With this configure line, "make tests" was giving segmentation fault with not much information in coredump. Then we realized that there is no support for gcov in glibc (https://sourceware.org/ml/libc-help/2017-09/msg00031.html)
There are suggestions to use oprofile  but that just gives functional coverage, we are looking for line coverage.
Does anyone tried supporting gcov for glibc, if yes, please share the patches or give us pointers to work on the same.

Thanks,
Avinash

Re: gcov support for glibc

[Carlos O'Donell]

On 07/19/2018 11:32 PM, Palleti, Avinash Reddy wrote:
> We are trying to get coverage analysis for glibc test cases, we tried
> below command to enable gcov support while building glibc.

There is no gcove support for glibc.

The core library implements the pieces that gcov needs to implement
coverage and so you have a circular dependency between the two which
limits gcov coverage of glibc.

Nobody that I know is working on this in the community.

It would be great to see a design from you to solve the problems.

A first pass solution is to enable coverage for just *part* of the
library like all things compiled under nptl/, and so you'll have to
* Add a configure option for --enable-coverage.
* Detect the configure option in nptl/Makefile and enable coverage.
* Add tests that show libpthread.so coverage is working.

-- 
Cheers,
Carlos.

RE: gcov support for glibc

[Palleti, Avinash Reddy]

> -----Original Message-----
> From: Carlos O'Donell [mailto:carlos@redhat.com]
> Sent: Friday, July 20, 2018 7:18 PM
> To: Palleti, Avinash Reddy <avinash.reddy.palleti@intel.com>; libc-
> help@sourceware.org
> Cc: Jasuja, Ritul <ritul.jasuja@intel.com>
> Subject: Re: gcov support for glibc
> 
> On 07/19/2018 11:32 PM, Palleti, Avinash Reddy wrote:
> > We are trying to get coverage analysis for glibc test cases, we tried
> > below command to enable gcov support while building glibc.
> 
> There is no gcove support for glibc.
> 
> The core library implements the pieces that gcov needs to implement coverage
> and so you have a circular dependency between the two which limits gcov
> coverage of glibc.
> 
> Nobody that I know is working on this in the community.
> 
> It would be great to see a design from you to solve the problems.

Thank you very much carlos. Will work on the same and update on this thread once we have design ready.

> 
> A first pass solution is to enable coverage for just *part* of the library like all
> things compiled under nptl/, and so you'll have to
> * Add a configure option for --enable-coverage.
> * Detect the configure option in nptl/Makefile and enable coverage.
> * Add tests that show libpthread.so coverage is working.
> 
> --
> Cheers,
> Carlos.

Re: gcov support for glibc

[Adhemerval Zanella]

On 20/07/2018 00:32, Palleti, Avinash Reddy wrote:
> Hi,
> 
> We are trying to get coverage analysis for glibc test cases, we tried below command to enable gcov support while building glibc.
> 
> CFLAGS="-ftest-coverage -fprofile-arcs -O2 -U_FORTIFY_SOURCE" CXXFLAGS="-ftest-coverage -fprofile-arcs" LD_FLAGS="-fprofile-arcs" ../configure --prefix=/opt/ --disable-werror  libc_cv_ctors_header=yes libc_cv_c_cleanup=yes
> 
> With this configure line, "make tests" was giving segmentation fault with not much information in coredump. Then we realized that there is no support for gcov in glibc (https://sourceware.org/ml/libc-help/2017-09/msg00031.html)
> There are suggestions to use oprofile  but that just gives functional coverage, we are looking for line coverage.
> Does anyone tried supporting gcov for glibc, if yes, please share the patches or give us pointers to work on the same.
> 
> Thanks,
> Avinash

I think you will need to do an assessment similar when we added -fstack-protector
support, where will need to identify which objects you will need to suppress the
gcov flags and any additional linking steps to get a functional build (maybe
by disabling on loader or adding any runtime required on a static build).

You can try to identify the problematic object which is causing the segfault by
using some points at [1]. Usually the most common issue is GDB can't find the
debug information (by issuing the linking manually) and one option is to use
--enable-hardcoded-path-in-tests.

[1] https://sourceware.org/glibc/wiki/Debugging/Development_Debugging