X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20120208102235.GA2796@qp9482>
References:	<33279157 DOT post AT talk DOT nabble DOT com> <20120207154359 DOT GA2952 AT qp9482> <20120207161428 DOT GB12159 AT calimero DOT vinschen DOT de> <4F31559B DOT 6060600 AT cs DOT utoronto DOT ca> <B0ED7173-1AC3-4B4E-8B79-3A9B22652684 AT Denis-Excoffier DOT org> <20120208090824 DOT GA1724 AT qp9482> <20120208092711 DOT GF25129 AT calimero DOT vinschen DOT de> <20120208102235 DOT GA2796 AT qp9482>
Date:	Wed, 8 Feb 2012 07:32:51 -0500
Message-ID:	<CA+sc5mkUpuFdtBjBVqZWqvj_n4T8ymxPsNFgpq+vt-TRep7f1g@mail.gmail.com>
Subject:	Re: cygwin-1.7.10-1 fork - address space needed by ... already in use
From:	Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, Feb 8, 2012 at 5:22 AM, Denis Excoffier wrote:
>
> I can reproduce.
>
> On my system (2012-02-07 snapshot instrumented), the following is able
> to exercise the fork failure any time.
>
> I do this from within a dedicated directory named "stc".
> Current shell seems indifferent. Here it is /bin/tcsh and
> i've tried with /bin/bash with the same result.
>
> % cat doit1
> #!/usr/bin/tcsh -f
> setenv PATH "/usr/bin"
> cp /usr/bin/cyggcc_s-1.dll .
> ls
> rm cyggcc_s-1.dll
> %

This is not going to work, period.  When you copy a DLL to the working
directory it will be that DLL that is used instead of the previously
loaded DLL.  It is the way the DLL search order works.  You'll see
failures and perhaps even lock up your OS.  Try this with the CYGWIN
DLL and you'll not be able to ls or rm.

>
> Hope this helps.
>

Ditto,

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -