[Bug c++/11644] Hang in throw when unloading a library
peter dot rost at freenet dot de
gcc-bugzilla@gcc.gnu.org
Tue Aug 19 15:32:00 GMT 2003
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 peter dot rost at freenet dot de 2003-08-19 15:32 -------
Subject: Re: Hang in throw when unloading a library
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.
On Tuesday 19 August 2003 17:15, you wrote:
> 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 gcc dot gnu dot org
> 2003-08-19 15:15 ------- Two possible problems that make your code not
> working:
>
> 1 You need g++ and libstdc++ that are thread-enabled.
> See this link for more info
> http://gcc.gnu.org/bugs.html#nonbugs_cxx
>
> 2 The exception is thrown inside __fini_lib through the
> function call chain:
> main -> unloadLib -> dlclose -> __fini_Lib
> If the dlclose in your C library is not built with
> exception unwinding, thrown exception cannot propagate
> back to main.
>
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
More information about the Gcc-bugs
mailing list