Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Problem with bash under cygwin 1.5.13
Date:	Thu, 3 Mar 2005 18:13:13 -0000
MIME-Version:	1.0
In-Reply-To:	<SERRANOYwcuBYW8LWui0000006f@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	03 Mar 2005 18:10:22.0653 (UTC) FILETIME=[4445DED0:01C5201C]
Message-ID:	<SERRANOsTLe0S7RXmvU00000073@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Dave Korn
>Sent: 03 March 2005 17:48

> ----Original Message----
>> From: Andrew Waltman
>> Sent: 03 March 2005 15:12


>> However, if I wait for eash instance of bash to come to a command prompt
>> I can start the 2nd, 3rd, etc. bash window. This behavior started after
>> updating the cygwin library to the latest revision (1.5.13).
> 
>   I'm running with current code (built from CVS earlier today) and I can't
> reproduce this.  I can fire up a dozen or more windows simultaneously and
> they all have no problems while running through their profile/.rc startup
> scripts.


.... but perhaps it would be worthwhile to add the "-x" flag to the line in
your cygwin.bat that invokes bash, and see if they're all crashing at the
same point, and if we think there's anything special about what it's doing
at that time that might offer us some clues ....



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -