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: Strange fork() behaviour under cygwin v1.3.1 Date: Tue, 22 May 2001 10:27:55 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: X-MS-Has-Attach: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-TNEF-Correlator: Thread-Topic: Strange fork() behaviour under cygwin v1.3.1 Thread-Index: AcDiVPVbhG1jR9vpSGaYYw9iARoPKwAAFKoA From: "Robert Collins" To: "Andrew de Quincey" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA15681 > -----Original Message----- > From: Andrew de Quincey [mailto:andrew@orbital.co.uk] > > Rob wrote > > > -----Original Message----- > > > From: Andrew de Quincey [mailto:andrew@orbital.co.uk] > > > Hi, I've been playing with the jabber server under win32... > > > and I've run > > > into a slight problem. The following program illustrates it: > > > > > > From the "non-preemptive-ness" & the lack of any pthread or > win32 thread > functions in it, it sounds like an entirely user-space > threading library. Oh. Well I suggest you build a debug pth library, and optionally a debug cygwin library (see the cvs source web page for build instructions), and see if pth is doing funky stuff that might confuse fork(). If no actual threads are involved, there shouldn't be any particular problems :]. Also update to cygwin 1.3.2 just-in-case. > > ****** IMPORTANT ******* > > When writing or testing threading code, ___always___ check > return values > > and error flags. > > That stuff was copied directly out of the jabber server source! :))) > Ouch. Uhmm, yeah. Ouch. Rob -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple