delorie.com/archives/browse.cgi | search |
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 |
Subject: | RE: Strange fork() behaviour under cygwin v1.3.1 |
Date: | Tue, 22 May 2001 10:11:45 +1000 |
MIME-Version: | 1.0 |
Message-ID: | <EA18B9FA0FE4194AA2B4CDB91F73C0EF79E7@itdomain002.itdomain.net.au> |
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: | AcDiUjsNEm0ETxglRe6oSdw1eSd8OwAANgLA |
From: | "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> |
To: | <cygwin AT cygwin DOT com> |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id UAA14694 |
> -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > 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] > >> 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |