From: jsturm@sigma6.com (Jeff Sturm) Subject: Re: fork + dlls 21 Aug 1998 19:48:34 -0700 Message-ID: <35DD879B.3C7E560B.cygnus.gnu-win32@sigma6.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Tim Newsham Cc: gnu-win32@cygnus.com 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. -- Jeff Sturm jsturm@sigma6.com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".