From: "Palleti, Avinash Reddy" <avinash.reddy.palleti@intel.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Cc: "Jasuja, Ritul" <ritul.jasuja@intel.com>
Subject: gcov support for glibc
Date: Fri, 20 Jul 2018 03:32:00 -0000 [thread overview]
Message-ID: <EBAEBC3AA1B73F4887F286A67235352365A89537@BGSMSX102.gar.corp.intel.com> (raw)
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
next reply other threads:[~2018-07-20 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 3:32 Palleti, Avinash Reddy [this message]
2018-07-20 13:47 ` Carlos O'Donell
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=EBAEBC3AA1B73F4887F286A67235352365A89537@BGSMSX102.gar.corp.intel.com \
--to=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).