X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 8 Oct 2009 12:02:09 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Thread related crash Message-ID: <20091008160209.GB28547@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4ACDCA99 DOT 9090400 AT cwilson DOT fastmail DOT fm> <20091008134822 DOT GD14389 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091008134822.GD14389@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, Oct 08, 2009 at 09:48:22AM -0400, Christopher Faylor wrote: >Uh, yeah. If you are not using Cygwin methods to start threads then it >is entirely likely that there will be problems, just like if you use >non-Cygwin methods to do I/O. OTOH, it is supposed to sort of work. That's what the code in init.cc which deals with the DLL_THREAD_ATTACH operation is supposed to be doing. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple