From: Carlos O'Donell <carlos@redhat.com>
To: "Palleti, Avinash Reddy" <avinash.reddy.palleti@intel.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Cc: "Jasuja, Ritul" <ritul.jasuja@intel.com>
Subject: Re: gcov support for glibc
Date: Fri, 20 Jul 2018 13:47:00 -0000 [thread overview]
Message-ID: <37a285de-4357-32b6-5112-eb08e24cc859@redhat.com> (raw)
In-Reply-To: <EBAEBC3AA1B73F4887F286A67235352365A89537@BGSMSX102.gar.corp.intel.com>
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.
next prev parent reply other threads:[~2018-07-20 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 3:32 Palleti, Avinash Reddy
2018-07-20 13:47 ` Carlos O'Donell [this message]
2018-07-20 16:54 ` Palleti, Avinash Reddy
2018-07-20 14:06 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37a285de-4357-32b6-5112-eb08e24cc859@redhat.com \
--to=carlos@redhat.com \
--cc=avinash.reddy.palleti@intel.com \
--cc=libc-help@sourceware.org \
--cc=ritul.jasuja@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).