From: Edgar Mobile <heideggm@hotmail.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Gcov produces too little output
Date: Wed, 25 Jan 2023 12:20:56 +0000 [thread overview]
Message-ID: <PH0PR84MB1835E3AD5201A4D45C40E080C7CE9@PH0PR84MB1835.NAMPRD84.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Greetings,
I try to instrument a large, multithreaded X64 Linux application with several shared objects for code instrumentation using g++ --coverage flag.
It creates a gcno file for every module but when I run the application almost no modules produce a gcda file. It should be noted that the binaries for the main application and the shared objects are moved to a different location to have them all in one place. But I cannot imagine which information it tries to access that fails the output.
The program outputs gcda files for some modules, but I do not see an obvious pattern.
I tried to end the application with SIGTERM and Ctrl-C.
Any ideas how to debug this?
Regards
reply other threads:[~2023-01-25 12:20 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=PH0PR84MB1835E3AD5201A4D45C40E080C7CE9@PH0PR84MB1835.NAMPRD84.PROD.OUTLOOK.COM \
--to=heideggm@hotmail.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).