Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 23 May 2001 21:31:03 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: core dev member please: Re: Strange fork() behaviour under cygwin v1.3.1 Message-ID: <20010523213103.A15986@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <01e701c0e3d7$5aa63650$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <01e701c0e3d7$5aa63650$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, May 24, 2001 at 08:26:03AM +1000 On Thu, May 24, 2001 at 08:26:03AM +1000, Robert Collins wrote: >Chris or another core dev member will need to comment on this. > >Personally, I'd suggest trotting off to the pth folk with a bug report. >(It works with pthreads and native win32 threads - so pth is the >problem). I was actually not responding because I don't have the slightest idea why this would fail, although it is my code. As I indicated, my test case for having fork run from another thread works fine. Sorry. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple