This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: [BUG] cygwin-1.3.3-2 -- making auto-import dlls
----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.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/