From:	cgf AT cygnus DOT com (Christopher G. Faylor)
Subject:	Re: fork + dlls
21 Aug 1998 01:31:39 GMT :
Message-ID:	<6riilr$t7g$1@cronkite.cygnus.com>
References:	<m0z9Gp9-0010zOC DOT cygnus DOT gnu-win32 AT malasada DOT lava DOT net>
X-Newsreader:	trn 4.0-test63 (15 March 1998)

In article <m0z9Gp9-0010zOC DOT cygnus DOT gnu-win32 AT malasada DOT lava DOT net>,
Tim Newsham <newsham AT lava DOT net> 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.
-- 
cgf AT cygnus DOT com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada

- Raw text -