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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [BUG] cygwin-1.3.3-2 -- making auto-import dlls X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 19 Sep 2001 12:44:45 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [BUG] cygwin-1.3.3-2 -- making auto-import dlls Thread-Index: AcFAtN+HNpvLg0W/QBaTRuN4cQDviAAABlDw From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id WAA10227 > -----Original Message----- > From: Christopher Faylor [mailto:cgf@redhat.com] > > >Solution: don't use auto-image-base. The overhead from relocation is > >quite low, why not let windows just do its thing. > > Even that is not guaranteed to fix this problem, though. > > Location of the cygwin heap is one of a few AFAIK inavoidable iffy > assumptions that cygwin makes. Cygwin's whole fork algorithm relies > on similar undocumented deterministic behavior. > Very true. The only *solution* is to ahve _every_ cygwin program depend on all the .dlls that every other cygwin program does, in the same order. Short of that happenning though :}.... Rob -- 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/