Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 19 Sep 2001 10:00:40 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [BUG] cygwin-1.3.3-2 -- making auto-import dlls
Message-ID:	<20010919100040.C13403@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<F2060Xn2Pi1Y7PeGbPn00001c09 AT hotmail DOT com>
Mime-Version:	1.0
In-Reply-To:	<F2060Xn2Pi1Y7PeGbPn00001c09@hotmail.com>
User-Agent:	Mutt/1.3.21i

On Wed, Sep 19, 2001 at 05:48:40AM -0700, Karl M wrote:
>What if we had a distinct dll for the heap (so the cygwin1.dll and 
>cygwin-something-heap.dll) and we statically size the heap as Chris 
>commented about. But...we select which size heap to use locally?

You're confused.  The size of the heap has nothing to do with anything.

Putting the heap in a DLL does not solve anything.  It's the cygheap
address that gets used that is a problem -- at least as far as this
auto-import situation is concerned.  Cygwin needs to be able to use an
address that is deterministic and Windows doesn't really guarantee that.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -