On Wed, May 23, 2007 at 09:33:58AM -0500, Matt Hoosier wrote: > > That's not really what I'm asking. Suppose there's a regular, > garden-variety shared library intended for any old application to use. > It's DSO is /usr/lib/libboo.so.0.1.2. Boo registers GTypes statically > like any other shared library does. > > Now some GModule comes along and happens to dynamically link against > libboo. The application which loads this module does not itself > require libboo. So at the time that the module is dlopen()ed under the > hood, libboo gets dynamically loaded also. > > What happens when the GModule is unloaded? Does libboo also get dumped > because the application itself doesn't directly link against > liboo.so.0.1.2, or does it stay resident forever? It is unloaded, well, at least on common platforms (not including MS Windows, have no idea what's going on there), I cannot guarantee every system does it though. If the libraries have exposed some static data, for instance through the GType system, things can break when they disappear. Yeti -- http://gwyddion.net/ _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
