Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Rolf Campbell <rcampbell AT tropicnetworks DOT com>
Subject: Re: CVS head bash problem
Date: Wed, 23 Apr 2003 21:49:35 -0400
Lines: 41
Message-ID: <b87fpo$dt$1@main.gmane.org>
References: <b84vjb$sqd$1 AT main DOT gmane DOT org> <b84q3m$drl$1 AT main DOT gmane DOT org> <20030423015402 DOT GB38081907 AT hpn5170x> <b84upp$qb5$1 AT main DOT gmane DOT org> <b84vjb$sqd$1 AT main DOT gmane DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20030423000357 DOT 007f9780 AT incoming DOT verizon DOT net> <20030423193236 DOT GC8396 AT redhat DOT com>
Reply-To: IDontLikePersonalReplies AT hotmail DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
In-Reply-To: <20030423193236.GC8396@redhat.com>

Christopher Faylor wrote:
> On Wed, Apr 23, 2003 at 12:03:57AM -0400, Pierre A. Humblet wrote:
> 
>>At 11:29 PM 4/22/2003 -0400, Christopher Faylor wrote:
>>
>>>A few debugging possibilities spring to mind here.
>>>
>>>Try running it under strace with a very large buffer size in (the -b
>>>option).  Attach to the hung process in strace or gdb.
>>>
>>>Does it also have problems with cygwin snapshots?  If not, then we need
>>>to see how you've configured your version of cygwin, what version of gcc
>>>you use, etc.
>>>
>>>If this is just a cvs thing (and that isn't really clear) then the old
>>>popular binary search through cvs might be useful to find out what
>>>change caused the problem.
>>>
>>>Also, send cygcheck output (as an attachment).  I suspect that you may
>>>be using CYGWIN=tty but we don't know what your setup is.
>>
>>I had sent a cygcheck output immediately after my initial report.
>>CYGWIN is unset.
>>
>>Contrary to Rolf I have never seen a hung process in this context.
> It just occurred to me that this is probably the old bash "reuse the
> pid" problem.  Bash is confused when pid numbers are reused in quick
> succession, which can be the case on Windows.  I thought that Corinna
> had turned on something in bash to work around this problem.  I wonder
> if it is no longer on in recent versions of bash or if the workaround
> doesn't work.
> 
> You can prove if this is the error or not by defining SLOW_PID_REUSE
> when compiling fork.cc.
That seems to have fixed the problem.  I tried 4950 commands, all of 
them worked (approx 1% failed before).  I will continue to use this 
build for a couple of days of 'real' work, and see if this problem stays 
away.

-Rolf



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