Subject: Re: fork + dlls
From: [email-masked] (Jeff Sturm)

21 Aug 1998 19:48:34 -0700
Message-ID: <[email-masked]>
References: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Tim Newsham <[email-masked]>
Cc: [email-masked]

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
[email-masked]
-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".