Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 19 Jul 2001 19:28:00 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: fork on win95 Message-ID: <20010719192800.B7237@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <005101c11036$06368800$806410ac AT local> <20010719112939 DOT A5093 AT redhat DOT com> <008001c1109d$40bca7e0$806410ac AT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <008001c1109d$40bca7e0$806410ac@local> User-Agent: Mutt/1.3.19i On Fri, Jul 20, 2001 at 07:53:31AM +1000, Robert Collins wrote: >----- Original Message ----- >From: "Christopher Faylor" > > >> Hmm. As I said, I actually tried my changes under Windows 95, so >> this will be difficult to track down, since I can't duplicate it. > >I'll see what sort of info I can generate for you, but I'm still pleading >time shortage right now. I'll generate a strace as a minimum (ie strace >sh -c ls) which should show the failure to fork(). Anything else that might >spark neurons? > >> Thanks for not saying "It worked fine in B20.1", by the way. :-) > >I forgot to mention that!. Doh!. Jeez. At the very *least* you could mention that fork works fine for you on linux. I need some reference point after all. cgf