This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: dlclose() doesn't unload any .so that uses Boost
- From: David Hagood <david dot hagood at gmail dot com>
- To: J <j at jabster dot pl>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Sun, 29 May 2011 06:51:00 -0500
- Subject: Re: dlclose() doesn't unload any .so that uses Boost
- References: <BANLkTin=7bTx6_9mxj=SOmt9pWLiXT9qvg@mail.gmail.com>
On Sun, 2011-05-29 at 01:32 +0200, J wrote:
> // compile with: g++ -ldl host.cpp -o host
<snip>
> // compile with: g++ -lboost_signals child.cpp -shared -fPIC -o libchild.so
Just for grins, what happens if you link main against Boost?
g++ -ldl host.cpp -o host -lboost_signals
It may be that since Boost is being pulled in to satisfy the child,
somehow that is preventing the child from being unloaded.
Of course, this isn't really a GCC question, but a libc/binutils
question, so you may do better over on that list.