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 12:14:59 +0000 [thread overview] Message-ID: <bug-100751-4-ZnyhWhGXl3@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 #5 from Gejoe <gejoed at rediffmail dot com> --- Running the program: ./a.out g When g is passed, return value is 8 When is passed, return value is 0 r When r is passed, return value is 8 When is passed, return value is 0 << the program is still running, waiting for next character entry>> Now if we see the sample-prog.c.gcov file , it shows : -: 16: do { -: 17: 4: 18: c = getchar(); 4: 19: result = isalnum(c); 4: 20: printf("When %c is passed, return value is %d\n", c, result); -: 21: 4: 22: if(c == 'g') 2: 23: __gcov_dump(); 2: 24: else if(c == 'r') #####: 25: __gcov_reset(); -: 26: 3: 27: }while(c != 'c'); Looking at line 25, it doesn't show the line is hit (by giving 'r' character during a.out run) nor are the counter values reset for the other lines. The count of 4,3,2 are seen for some lines because of a previous a.out run.
next prev parent reply other threads:[~2021-05-25 12:14 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 2021-05-25 12:14 ` gejoed at rediffmail dot com [this message] 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-ZnyhWhGXl3@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: linkBe 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).