This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: shared libraries & exceptions
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Nathan Myers <ncm-nospam at cantrip dot org>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
- Date: Tue, 04 Feb 2003 14:01:01 -0800
- Subject: Re: shared libraries & exceptions
--On Monday, February 03, 2003 01:37:37 PM -0800 Nathan Myers
<ncm-nospam@cantrip.org> wrote:
So the question is, is there any (non-portable!) entry point that
can be called by the C code, before or after the dlopen, that will
ensure proper initialization of the exception apparatus?
In GCC 3, it shouldn't make any different what the main program is
written in. As long as libgcc is linked in, statically or dynamically,
its initializers will run, and that will set up the exception handling
stuff for the application. The initializers for the plugin will register
the right PC range tables and things should be good to go. (Unloading
the plugin may be more problematic...)
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com