Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <00a601c0b0b4$2ede8230$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <002701c0af7c$fac67710$0200a8c0 AT lifelesswks> <20010318120654 DOT C12880 AT redhat DOT com> <007f01c0aff1$9889f110$0200a8c0 AT lifelesswks> <00f401c0b064$f3a15a70$0200a8c0 AT lifelesswks> <20010319124545 DOT C18807 AT redhat DOT com> Subject: Re: pthreads Date: Tue, 20 Mar 2001 07:35:47 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 19 Mar 2001 20:30:09.0854 (UTC) FILETIME=[64866DE0:01C0B0B3] ----- Original Message ----- From: "Christopher Faylor" To: Sent: Tuesday, March 20, 2001 4:45 AM Subject: Re: pthreads > On Mon, Mar 19, 2001 at 10:08:27PM +1100, Robert Collins wrote: > >I'm not 100% sure we follow the calling thread's state rather than the > >mainthreads state, but I'll look into that. > > We should duplicate the calling thread's state. This was a customer > problem report a couple of years ago and I went to great efforts to fix > it. If we don't do that then we definitely won't duplicate the main > thread's state, so the alternative is that we would probably crash > or hang, or something. > > cgf > Thanks. I'll assume we do, and confirm when we I look at the pthread_fork functions. Rob