This is the mail archive of the
mailing list for the Cygwin project.
Re: fork + dlls
- To: Tim Newsham <newsham at lava dot net>
- Subject: Re: fork + dlls
- From: Jeff Sturm <jsturm at sigma6 dot com>
- Date: Fri, 21 Aug 1998 10:43:39 -0400
- CC: gnu-win32 at cygnus dot com
- References: <m0z9Gp9-0010zOC@malasada.lava.net>
Are you using dlopen() or LoadLibrary()? If you use the latter fork()
does not (and probably cannot) preserve dynamic libraries.
Tim Newsham wrote:
> When you manually load a dll, and then perform a fork, the dll
> is not accessible from the child process. When you think about what
> is going on here, it makes sense. My question though is, is this the
> way fork should behave? Or should (could) the fork code reload the
> dll in the child process after a fork? It seems that this would
> more closely follow the expected fork semantics.
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".