This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11644] Hang in throw when unloading a library
- From: "lerdsuwa at users dot sourceforge dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Aug 2003 09:42:36 -0000
- Subject: [Bug c++/11644] Hang in throw when unloading a library
- References: <20030723121224.11644.peter.rost@freenet.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11644
------- Additional Comments From lerdsuwa at users dot sourceforge dot net 2003-08-24 09:42 -------
Subject: Re: Hang in throw when unloading a library
You can use GCC option -fexceptions during compilation of
C code to make it support exception unwinding. But after
looking at the glibc dlcose source code, I think throwing
exception through this function could leave some glibc
internal data structure messed up. You should catch all
exceptions in your library __fini_Lib instead.
--Kriang
Peter Rost wrote:
>well, it sounds good, but
>
>
>1. how can i determine if my dlclose is built with/without exception
>unwinding?
>2. for me it's very mysterious, that the debian-compiled-version of gcc 2.95
>doesnot have any problems with but gcc 3.x has them!? so, are there some more
>changes at dlclose which can produce the behaviour?
>
>thanks a lot for your help, peter.
>
>
>