RE: Strange fork() behaviour under cygwin v1.3.1

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> On Tue, May 22, 2001 at 09:56:01AM +1000, Robert Collins 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:
> >> 
> >> +++++++++++++++++++++++++++++++++++++++++++++++++
> >> #include <pth.h>
> >
> >Whats <pth.h> ? If it's the GNU portable threads library, 
> and it's using
> >a native thread library instead of 100% emulated threads, 
> make sure its
> >using pthreads, not win32 threads. (Explanation: Cygwin is 
> ignorant of
> >direct win32 thread calls you might make, but it knows about 
> pthreads).
> 
> That's not entirely true.  Cygwin should be aware of the fact that the
> fork is running in a thread and should duplicate the thread state
> correctly.
> 
> The end result will be a child process with a main thread 
> which is a copy
> of the thread that called fork in the parent.

Then we're looking at a bug in cygwin w.r.t. pth. As I cannot look at
the pth source without being unable to contribute to cygwin's thread
code anymore.. someone else will have to debug this.
 
Rob

> 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