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 22:22:36 -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: <20010523222236.A28122@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from robert.collins@itdomain.com.au on Thu, May 24, 2001 at 11:45:24AM +1000 On Thu, May 24, 2001 at 11:45:24AM +1000, Robert Collins wrote: >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> >> 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. > >Ditto - in fact you did respond before. I was referring to the fact that >pth apparently diddles the stack among other things? Right. That is what I wasn't responding to. :-) I'm not particularly interested in debugging another application's use of a thread. Sorry. I can't even offer any suggestions about how to debug this. If it is failing at this level then something is fundamentally wrong. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple