Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 11 Jun 2002 11:02:20 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Making cygwin1.dll, unrelocateable. Message-ID: <20020611150220.GG32286@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20020610015928 DOT GA31401 AT redhat DOT com> <20020611125919 DOT GD1572 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020611125919.GD1572@tishler.net> User-Agent: Mutt/1.3.23.1i On Tue, Jun 11, 2002 at 08:59:19AM -0400, Jason Tishler wrote: >Chris, > >On Sun, Jun 09, 2002 at 09:59:28PM -0400, Christopher Faylor wrote: >> I think we agreed a while ago that it would be a good idea to make the >> cygwin DLL always occupy the same space in memory. I know that this >> would be a good thing for cases where c++ method pointers are stored in >> shared memory. > >The above will remove the special case in setup.exe's rebase >functionality to skip rebasing the Cygwin DLL. Although, can we change >the ImageBase from 0x61000000 to 0x60000000 to avoid having to rebase >around it? Why does that help? IIRC when I chose the 0x61000000 location, I did so because using 0x60000000 (which, I think, is the "correct" proposed location for cygwin) conflicted with some other Windows DLL. cgf