public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rc452860 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110072] New: __gcov_dump cannot generate gcda for so files opened with dlopen when gcc version is later than 5.1.0 Date: Thu, 01 Jun 2023 08:16:52 +0000 [thread overview] Message-ID: <bug-110072-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110072 Bug ID: 110072 Summary: __gcov_dump cannot generate gcda for so files opened with dlopen when gcc version is later than 5.1.0 Product: gcc Version: 4.8.5 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rc452860 at gmail dot com Target Milestone: --- Created attachment 55229 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55229&action=edit example When the version of gcc is lower than 5.1.0, __gcov_dump cannot generate gcda files for the so files opened by dlopen. See attachment for sample project. After comparing the different versions of GCC code, I found that gcc before 5.1.0 stored counter data in gcov_list, while later versions of GCC stored it in __gcov_master. The two versions are defined as follows: gcc4.8.5 in libgcc/libgcov.c ``` /* Chain of per-object gcov structures. */ static struct gcov_info *gcov_list; ``` gcc8.5.0 in libgcc/libgcov-driver.c ``` /* Exactly one of these will be live in the process image. */ struct gcov_master __gcov_master = {GCOV_VERSION, 0}; ```
next reply other threads:[~2023-06-01 8:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 8:16 rc452860 at gmail dot com [this message] 2023-06-01 8:47 ` [Bug gcov-profile/110072] " rc452860 at gmail dot com 2023-06-01 13:43 ` pinskia at gcc dot gnu.org
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-110072-4@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).