Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 21 May 2001 20:06:57 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Strange fork() behaviour under cygwin v1.3.1
Message-ID: <20010521200657.C17520@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF79E6 AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF79E6@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Tue, May 22, 2001 at 09:56:01AM +1000

On Tue, May 22, 2001 at 09:56:01AM +1000, Robert Collins wrote:
>> -----Original Message-----
>> From: Andrew de Quincey [mailto:andrew AT orbital DOT co DOT uk]
>> Sent: Tuesday, May 22, 2001 9:01 AM
>> To: cygwin AT cygwin DOT 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.

cgf

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