From: Kevin Kress <kevin.kress@comdev.cc>
To: gcc-help@gcc.gnu.org
Subject: Assistance with gcov
Date: Wed, 17 Jul 2002 16:33:00 -0000 [thread overview]
Message-ID: <1026948806.5757.7.camel@leftfield> (raw)
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
I am looking for assistance with the gcov program and related gcc
flags. I posted a question 2 days ago but got no response. I have
since discovered that the program I was having problems with does in
fact generate .da file about 1 out of every 5 times it is run.
I am looking for some insights about how to go about debugging this, who
might know anything about this problem or where to find more on code
inserted when the code coverage flags in gcc are enabled.
--Kevin
--
Kevin Kress (Software Engineer)
COM DEV Broadband
San Luis Obispo, CA
Phone: 805-544-1089
Fax: 805-544-2055
GnuPG/PGP Key ID: 8A811ECC
Fingerprint : D244 8D76 327D F7B8 DAE6 FF72 30F0 694B 8A81 1ECC
See Keyserver: http://www.keyserver.net/en/findkey.html
(search for "Kevin Kress" or "0x8A811ECC")
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2002-07-17 23:33 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=1026948806.5757.7.camel@leftfield \
--to=kevin.kress@comdev.cc \
--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).