X-Spam-Check-By: sourceware.org Date: Wed, 18 Jan 2006 11:31:28 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Intermittent cygwin heap allocation problem Message-ID: <20060118163128.GC15870@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <43CE4834 DOT 1010702 AT hones DOT org DOT uk> <20060118160845 DOT GA15870 AT trixie DOT casa DOT cgf DOT cx> <43CE6A41 DOT 8050208 AT hones DOT org DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43CE6A41.8050208@hones.org.uk> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Wed, Jan 18, 2006 at 04:18:09PM +0000, Cliff Hones wrote: >Can this explain failures to initialize executables which don't use threads? >I don't know, but I wouldn't have thought 'ls' uses threads. Every cygwin application (and probably every windows application) uses threads. The above scenario only happens when there is a system thread starting before cygwin is initialized but there are sometimes mysterious threads being started during process initialization. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/