Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Subject: RE: core dev member please: Re: Strange fork() behaviour under cygwin v1.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 24 May 2001 11:45:24 +1000 content-class: urn:content-classes:message Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: core dev member please: Re: Strange fork() behaviour under cygwin v1.3.1 Thread-Index: AcDj8xEZo1pJIALUSUaFNUwe5e4G6QAAAqkQ From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id WAA10783 > -----Original Message----- > From: Christopher Faylor [mailto:cgf@redhat.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? Rpb > > Sorry. > > cgf > > -- > Want to unsubscribe from this list? > Check out: http://cygwin.com/ml/#unsubscribe-simple > > -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple