X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Intermittent cygwin heap allocation problem
Date:	Wed, 18 Jan 2006 16:41:08 -0000
MIME-Version:	1.0
In-Reply-To:	<20060118163128.GC15870@trixie.casa.cgf.cx>
Message-ID:	<SERRANOY6hlHK91rGGX000001bb@SERRANO.CAM.ARTIMI.COM>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Christopher Faylor wrote:
> 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


  I wonder if they sometimes get started from DllEntry of hook dlls?  That
could account for some of the AV/PFW problems we see reported.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/

- Raw text -