This is the mail archive of the
mailing list for the Cygwin project.
Re: fork + dlls
- To: gnu-win32 at cygnus dot com
- Subject: Re: fork + dlls
- From: cgf at cygnus dot com (Christopher G. Faylor)
- Date: 21 Aug 1998 01:31:39 GMT
- Newsgroups: cygnus.gnu-win32
- Organization: Cygnus Solutions
- References: <m0z9Gp9-0010zOC.firstname.lastname@example.org>
- Stamped: newsgate-cygnus
In article <m0z9Gp9-0010zOC.email@example.com>,
Tim Newsham <firstname.lastname@example.org> 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.
If you use UNIX semantics (dlopen) to load the .dll then the .dll
should be automatically loaded on a fork.
email@example.com "Everything has a boolean value, if you stand
http://www.cygnus.com/ far enough away from it." -- Galena Alyson Canada
For help on using this list (especially unsubscribing), send a message to
"firstname.lastname@example.org" with one line of text: "help".