delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/08/21/14:26:28

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: fork + dlls
21 Aug 1998 14:26:28 -0700 :
Message-ID: <01BDCCE1.270615A0.cygnus.gnu-win32@sos>
To: "gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>,
"'Tim Newsham'"
<newsham AT lava DOT net>

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.
>

The dll will be reloaded on fork, if dll's startup code performs neccessary 
initialization. See http://www.cygnus.com/misc/gnu-win32/dl-docs.html for 
details.

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019