Re: g_module_close() did not really unload the module ?

[Kuang-Chun Cheng <kccheng LinuxDAQ-Labs com>]

Sorry, the problem is in my application, not g_module_open().
I do g_module_open() for the same .so file twice ...

KC

On Sun, Mar 29, 2009 at 3:40 AM, Kuang-Chun Cheng
<kccheng linuxdaq-labs com> wrote:
> Hi,
>
> I did the following test:
>
> g_module_open()
> ... do something make sure g_module_open() success ...
> g_module_close()
> ... remove the .so file
> g_module_open()
>
> And I found the 2nd g_module_open() still success even the .so file
> is removed !!!
> It looks like the g_module_open() will cache the library.
> I did not use g_module_make_resident().
> Is this normal ? or a bug ?  How to fix this ?
> Thanks a lot.
>
> ps. I'm using glib2-2.14.1-4.2 (OpenSuSE 10.3)
>
> Regards
> KC
>