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
Message-ID: <010a01c140fd$13e3e310$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin AT cygwin DOT com>
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F199 AT itdomain002 DOT itdomain DOT net DOT au> <20010918225336 DOT G8924 AT redhat DOT com>
Subject: Re: [BUG] cygwin-1.3.3-2 -- making auto-import dlls
Date: Wed, 19 Sep 2001 21:20:23 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 19 Sep 2001 11:28:40.0144 (UTC) FILETIME=[3B281D00:01C140FE]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
>
> Just in case anyone knows how to do this:
>
> If I could *reserve* but not allocate a fixed amount of memory for the
> cygwin heap on DLL load, this would fix the problem.  I could
> conceivably add another 512K of allocated memory to the end of every
> cygwin DLL load but that just didn't seem right.
>
> I played around with a lot of ld script file settings trying to
achieve
> this effect but I could never do it.  I wouldn't be surprised that
> Windows doesn't allow actually it because the concept requires a
> sophisticated run time loader.

wrong list .... isn't this a binutils question? :]. Seriously though,
someone there may well be able to answer this. On a related note, I
didn't realise the fix would be so simple. My understanding was that the
variables in question cannot cope with the address's being different
between parent and child, and tacking a 1/2Mb on the end of the
cygwin1.dll address space wouldn't affect that - that area would get
relocated too. perhaps I'm missing something 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/