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

[Christopher Faylor <cgf at redhat dot com>]

On Mon, May 21, 2001 at 08:06:57PM -0400, Christopher Faylor wrote:
>On Tue, May 22, 2001 at 09:56:01AM +1000, Robert Collins wrote:
>>> -----Original Message-----
>>> From: Andrew de Quincey [mailto:andrew@orbital.co.uk]
>>> Sent: Tuesday, May 22, 2001 9:01 AM
>>> To: cygwin@cygwin.com
>>> Subject: Strange fork() behaviour under cygwin v1.3.1
>>> 
>>> 
>>> 
>>> 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.

I just checked and this still works in 1.3.2 for at least a simple test case.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple