public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19985] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit ()
Date: Fri, 11 Mar 2005 01:32:00 -0000	[thread overview]
Message-ID: <20050311013224.22331.qmail@sourceware.org> (raw)
In-Reply-To: <20050215214329.19985.lothar@xcerla.com>


------- Additional Comments From janis at gcc dot gnu dot org  2005-03-11 01:32 -------
The submitter's testcase works if function __gcov_init in libgcov.c
is declared hidden.  Probably all of the __gcov* symbols ought to be
hidden; I'll work on a patch to hide that symbol and others that seem
appropriate.
                                                                                
Possible workaround:
                                                                                
The linker's -E option exports all global symbols from the executable
to the dynamic symbol table.  A subset of global symbols can be
exported by using -E along with --version-script to list symbols to
export.  Depending on how many symbols a shared object needs to access
from a shared object, this might be a reasonable workaround.
I consulted an expert, and unfortunatly there doesn't seem to be a way
to say "export all symbols except this small list".

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19985


  parent reply	other threads:[~2005-03-11  1:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  3:32 [Bug c++/19985] New: " lothar at xcerla dot com
2005-02-16  3:32 ` [Bug middle-end/19985] " pinskia at gcc dot gnu dot org
2005-02-16  3:37 ` lothar at xcerla dot com
2005-02-16  3:48 ` pinskia at gcc dot gnu dot org
2005-03-01  1:03 ` lothar at xcerla dot com
2005-03-01  1:16 ` pinskia at gcc dot gnu dot org
2005-03-01  1:23 ` lothar at xcerla dot com
2005-03-08  3:59 ` renierm at us dot ibm dot com
2005-03-08 14:52 ` pinskia at gcc dot gnu dot org
2005-03-10 19:42 ` janis at gcc dot gnu dot org
2005-03-11  1:32 ` janis at gcc dot gnu dot org [this message]
2005-03-11 23:54 ` janis at gcc dot gnu dot org
2005-03-15 17:22 ` [Bug middle-end/19985] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-03-25  0:09 ` janis at gcc dot gnu dot org
2005-04-21  5:01 ` mmitchel at gcc dot gnu dot org
2005-05-02 18:03 ` cvs-commit at gcc dot gnu dot org
2005-05-02 18:05 ` cvs-commit at gcc dot gnu dot org
2005-05-02 18:09 ` cvs-commit at gcc dot gnu dot org
2005-05-02 19:02 ` pinskia at gcc dot gnu dot org
2005-06-21 20:31 ` matz at suse dot de

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=20050311013224.22331.qmail@sourceware.org \
    --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).