Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 6 Aug 2002 20:22:03 +0100
From:	"Steven O'Brien" <steven DOT obrien2 AT ntlworld DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [RFC] an alternative to rebasing [recall]
Message-Id:	<20020806202203.2286de17.steven.obrien2@ntlworld.com>
Mime-Version:	1.0

Jason

> On Tue, Aug 06, 2002 at 09:38:52AM +0100, Steven O'Brien wrote:
> > So rebase is the only solution available right now.
>                                          ^^^^^^^^^
> 
> Are you giving up?  Or, will you try to find another solution?

I have no new ideas to investigate at present. The problem is that the
cygwin algorithm in dll_init.cc is able to force windows to use a higher
relocation address, but cannot force it to relocate lower than the one
it finds by default. I was hoping that by always loading from low
address to high then we could side-step this problem, and indeed in many
cases this does work. But sometimes windows relocates to a higher
address than it did in the parent, and we are just not able to correct
this.

If anyone knows where I can find a specification of the windows
relocation algorithm, then maybe I can find a mechanism to implement
true fork() semantics, or prove once and for all that it just cannot be
done. Until then, or some other flash of inspiration, I will be working
on some of the other (many) outstanding issues with my gnome port.

Steven

--
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/

- Raw text -