Re: fork + dlls

[cgf at cygnus dot com (Christopher G. Faylor)]

In article <m0z9Gp9-0010zOC.cygnus.gnu-win32@malasada.lava.net>,
Tim Newsham <newsham@lava.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@cygnus.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
"gnu-win32-request@cygnus.com" with one line of text: "help".