This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Strange fork() behaviour under cygwin v1.3.1
- To: "Andrew de Quincey" <andrew at orbital dot co dot uk>,<cygwin at cygwin dot com>
- Subject: RE: Strange fork() behaviour under cygwin v1.3.1
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Tue, 22 May 2001 10:27:55 +1000
> -----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