Re: dlclose() vs fork()

2017-03-22 Thread Corinna Vinschen
On Mar 22 08:44, Alexey Sokolov wrote: > Thanks Corinna for the quick fix, > The user confirmed it's working now with the snapshot. > > 21.03.2017 13:42, Corinna Vinschen пишет: > > On Mar 21 09:03, Alexey Sokolov wrote: > > > Hello, > > > If the same DLL is dlopen()ed several times, dlclose()

Re: dlclose() vs fork()

2017-03-22 Thread Alexey Sokolov
Thanks Corinna for the quick fix, The user confirmed it's working now with the snapshot. 21.03.2017 13:42, Corinna Vinschen пишет: On Mar 21 09:03, Alexey Sokolov wrote: Hello, If the same DLL is dlopen()ed several times, dlclose() will actually unload the DLL only after the same number of

Re: dlclose() vs fork()

2017-03-21 Thread Corinna Vinschen
On Mar 21 09:03, Alexey Sokolov wrote: > Hello, > If the same DLL is dlopen()ed several times, dlclose() will actually > unload the DLL only after the same number of calls to dlclose(). > > This works fine in cygwin, until we add fork(). > > It looks like in the child process the counters of

dlclose() vs fork()

2017-03-21 Thread Alexey Sokolov
Hello, If the same DLL is dlopen()ed several times, dlclose() will actually unload the DLL only after the same number of calls to dlclose(). This works fine in cygwin, until we add fork(). It looks like in the child process the counters of inherited DLLs are set to 1, so the first dlclose()