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:33:31 -0000
MIME-Version:	1.0
In-Reply-To:	<20060118160845.GA15870@trixie.casa.cgf.cx>
Message-ID:	<SERRANO11HZv7FDwfCr000001ba@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:

> Actually, this kind of error is more likely to be caused by a thread
> starting prior to cygwin initialization and grabbing cygwin's heap area
> to use for its stack.  

  Oh, of course!  2 meg of allocation is going to throw everything waaaay off!


    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 -