Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3BA8A877.48700BE3@syntrex.com> Date: Wed, 19 Sep 2001 16:15:19 +0200 From: Pavel Tsekov Organization: Syntrex Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [BUG] cygwin-1.3.3-2 -- making auto-import dlls References: <20010919100040.C13403@redhat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit What's the exact purpose of this requirement ? Christopher Faylor wrote: > > 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/