public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gejoed at rediffmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/100751] __gcov_dump and __gcov_reset usage
Date: Tue, 25 May 2021 10:57:13 +0000	[thread overview]
Message-ID: <bug-100751-4-WDARbfaPHd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100751-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100751

--- Comment #4 from Gejoe <gejoed at rediffmail dot com> ---
(In reply to Martin Liška from comment #3)
> > For the second time and then onwards, __gcov_dump() invocation (by giving
> > 'g' character during the a.out run) doesn't happen.
> 
> Yes, one can call __gcov_dump only once per run.

So, I understand that __gcov_dump could be used only after doing all the
testing with the application ,i.e- towards the end to get the profile/coverage
info. Am I right?


> > Another thing is  that, __gcov_reset() also doesn't appear to work. I tried
> > giving the character 'r' during the run of the program but couldn't see the
> > counters getting reset to 0 in the sample-prog.gcov file. The previous
> > values of lines covered were there.
> 
> No, __gcov_reset resets run-time counters (profile collected so far during
> an application run). If you want to clear profile, then simply remove .gcda
> files.

Resetting run-time counters - does that mean it would not get reflected in
.gcda files or the .c.gcov file contents created by gcov (assuming that the
application a.out is still on run )?

  parent reply	other threads:[~2021-05-25 10:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  6:54 [Bug gcov-profile/100751] New: " gejoed at rediffmail dot com
2021-05-25  6:58 ` [Bug gcov-profile/100751] " gejoed at rediffmail dot com
2021-05-25  7:01 ` gejoed at rediffmail dot com
2021-05-25  7:56 ` marxin at gcc dot gnu.org
2021-05-25 10:57 ` gejoed at rediffmail dot com [this message]
2021-05-25 12:14 ` gejoed at rediffmail dot com
2021-05-25 12:52 ` marxin at gcc dot gnu.org
2021-05-25 12:53 ` marxin at gcc dot gnu.org
2021-05-25 18:40 ` gejoed at rediffmail dot com
2021-05-26  7:31 ` marxin at gcc dot gnu.org
2021-05-26  7:34 ` cvs-commit at gcc dot gnu.org
2021-05-26  7:34 ` marxin at gcc dot gnu.org
2021-05-26 15:13 ` gejoed at rediffmail dot com
2021-05-27 13:53 ` gejoed at rediffmail dot com
2021-05-27 13:57 ` marxin at gcc dot gnu.org
2021-05-27 13:58 ` marxin at gcc dot gnu.org
2021-05-28  5:49 ` gejoed at rediffmail dot com
2021-05-28  6:15 ` gejoed at rediffmail dot com
2021-05-28  6:18 ` gejoed at rediffmail dot com
2021-05-28  6:22 ` gejoed at rediffmail dot com
2021-05-28  7:30 ` marxin at gcc dot gnu.org
2021-05-28  9:57 ` gejoed at rediffmail dot com
2021-05-28 11:38 ` cvs-commit at gcc dot gnu.org
2021-05-28 11:41 ` marxin at gcc dot gnu.org
2021-06-01  5:25 ` gejoed at rediffmail dot com

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=bug-100751-4-WDARbfaPHd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).