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 Date: Mon, 19 Mar 2001 12:45:45 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: pthreads Message-ID: <20010319124545.C18807@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <002701c0af7c$fac67710$0200a8c0 AT lifelesswks> <20010318120654 DOT C12880 AT redhat DOT com> <007f01c0aff1$9889f110$0200a8c0 AT lifelesswks> <00f401c0b064$f3a15a70$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <00f401c0b064$f3a15a70$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Mon, Mar 19, 2001 at 10:08:27PM +1100 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