Re: GModule unloading
- From: Paul Davis <paul linuxaudiosystems com>
- To: Matt Hoosier <matt hoosier gmail com>
- Cc: gtk-list gnome org
- Subject: Re: GModule unloading
- Date: Wed, 23 May 2007 10:50:41 -0400
On Wed, 2007-05-23 at 09:33 -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?
its a reasonable question. a prior question, however: why are you
worrying about this?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]