Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 27 Sep 1999 16:35:42 -0400
To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu>,
        Kevin Wright <kwright AT aspectdv DOT com>, cygwin AT sourceware DOT cygnus DOT com
Subject: Re: fork/exec fixed? [was Re: How to build static lib's]
Message-ID: <19990927163542.A1482@cygnus.com>
Mail-Followup-To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>,
	Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu>,
	Kevin Wright <kwright AT aspectdv DOT com>, cygwin AT sourceware DOT cygnus DOT com
References: <199909271931 DOT OAA11630 AT mercury DOT xraylith DOT wisc DOT edu> <37EFD216 DOT 8AA5858A AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <37EFD216.8AA5858A@ece.gatech.edu>; from Charles S. Wilson on Mon, Sep 27, 1999 at 04:22:46PM -0400

On Mon, Sep 27, 1999 at 04:22:46PM -0400, Charles S. Wilson wrote:
>Mumit Khan wrote:
>
>> 
>> This problem is due to a bug in cygwin-b20, and is fixed in recent
>> snapshots. In most cases, it is quite harmless (unless you're creating
>> subprocesses using fork/exec, in which case odd things may happen).
>> 
>
>Does this mean that the old fork/exec problem that plagued cygwin-perl a
>while back is fixed in recent snapshots? Not fixed? Partially fixed?
>
>Reference: "fork + dlls" thread on May 21-23, 1999.

I don't think so.  I investigated this a while ago.  I looks like the problem
is due to the fork code loading the DLLs in the wrong order which causes the
DLLs in the child to be loaded in different locations than the parent.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com