From: Soumyaranjan Sabat <srs.sabat@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Support and additional information to use GCOV
Date: Tue, 19 Oct 2021 11:28:12 +0530 [thread overview]
Message-ID: <CAP97gS-uUkSea7Ax57-1J-TkrcWNVfgTPrkvY3=HyQC7LO_+aQ@mail.gmail.com> (raw)
Hello Team,
Had a couple of queries for use of gcov. Requesting for your help !!
1. There are 2 configurations for a file [trigger.c] due to a macro i.e
#define TRIGGER which can have values ON and OFF [ and hence 2
configurations ]. By 2 configurations, it is meant that
a. Configuration 1 : trigger.c - #define TRIGGER ON
b. Configuration 1 : trigger.c - #define TRIGGER OFF
Due to 2 different macros, different parts of code are enabled. But a
consolidated coverage report is required, i.e which combines both coverage
reports of configuration 1 and configuration 2 into a single report to show
if any part of the code is missed to test.
Is this possible by directly using gcov and/or Gcovr and/or Gcov-tool
and/or Gcov-dump?
2. Is it possible to check for coverage of a particular file? i.e in a
project there are multiple files such as trigger.c , trigger_internal.c etc
but consolidated coverage of only trigger.c is required.
Please advise how to proceed on these 2 queries.
Regards,
Soumyaranjan
reply other threads:[~2021-10-19 5:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAP97gS-uUkSea7Ax57-1J-TkrcWNVfgTPrkvY3=HyQC7LO_+aQ@mail.gmail.com' \
--to=srs.sabat@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).