Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/