public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghost at cs dot msu dot su" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/23628] Typeinfo comparison code easily breaks shared libs Date: Tue, 30 Aug 2005 13:17:00 -0000 [thread overview] Message-ID: <20050830131021.27875.qmail@sourceware.org> (raw) In-Reply-To: <20050829194742.23628.mmarcus@emarcus.org> ------- Additional Comments From ghost at cs dot msu dot su 2005-08-30 13:10 ------- To clarify what Marcus said, I've made a small example: http://zigzag.cs.msu.su/~ghost/rtti-4.0 The third party library 'libhelper.so' is built with default visibility. I want my own library 'libhelper2.so' to be built with hidden visibility. However, my library contains this: try { foo(); } catch(my_exception& e) { Both 'foo' and 'my_exception' are defined in libhelper.so -- third party library. So, if I build my library with hidden visibility, 'catch' no longer works. I have two solutions: 1. Add push/pops in other library headers, which is very inconvenient. 2. Create wrapper headers and add push/pops there, which is very inconvenient. And if I forget just a single header (which was probably added in the last version of third party library), I'll get hard to diagnose bug. Usability cost is indeed high. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23628
next prev parent reply other threads:[~2005-08-30 13:10 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-29 19:55 [Bug c++/23628] New: " mmarcus at emarcus dot org 2005-08-29 19:58 ` [Bug c++/23628] " pinskia at gcc dot gnu dot org 2005-08-29 19:59 ` pinskia at gcc dot gnu dot org 2005-08-29 20:23 ` mmarcus at emarcus dot org 2005-08-29 20:27 ` mmarcus at emarcus dot org 2005-08-29 20:30 ` pinskia at gcc dot gnu dot org 2005-08-29 20:31 ` pinskia at gcc dot gnu dot org 2005-08-29 20:34 ` pinskia at gcc dot gnu dot org 2005-08-29 20:40 ` pinskia at gcc dot gnu dot org 2005-08-29 20:49 ` mmarcus at emarcus dot org 2005-08-29 20:56 ` pinskia at gcc dot gnu dot org 2005-08-29 20:57 ` pinskia at gcc dot gnu dot org 2005-08-29 21:01 ` mmarcus at emarcus dot org 2005-08-29 21:05 ` mmarcus at emarcus dot org 2005-08-29 21:11 ` pinskia at gcc dot gnu dot org 2005-08-29 21:32 ` mmarcus at emarcus dot org 2005-08-29 21:32 ` Andrew Pinski 2005-08-29 21:57 ` pinskia at physics dot uc dot edu 2005-08-29 22:14 ` mmarcus at emarcus dot org 2005-08-30 13:17 ` ghost at cs dot msu dot su [this message] 2005-08-30 13:44 ` gdr at integrable-solutions dot net 2005-08-31 7:19 ` ghost at cs dot msu dot su 2005-08-31 14:21 ` pinskia at gcc dot gnu dot org 2005-08-31 14:39 ` ghost at cs dot msu dot su 2005-08-31 14:56 ` gdr at integrable-solutions dot net 2005-09-01 8:35 ` mmarcus at emarcus dot org 2005-09-01 10:42 ` s_gccbugzilla at nedprod dot com [not found] <bug-23628-10681@http.gcc.gnu.org/bugzilla/> 2006-01-21 21:02 ` rjohnson at dogstar-interactive dot com 2006-01-21 21:45 ` gdr at cs dot tamu dot edu 2006-09-18 21:02 ` geoffk at gcc dot gnu dot 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=20050830131021.27875.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: 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).