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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<108401c18607$e862b2c0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Jason Tishler" <jason AT tishler DOT net>, "Cygwin" <cygwin AT sources DOT redhat DOT com>
Cc:	"Michael Hudson" <mwh AT python DOT net>, <david_abrahams AT users DOT sourceforge DOT net>
References:	<20011210102715 DOT A1312 AT dothill DOT com>
Subject:	Re: dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...)
Date:	Sun, 16 Dec 2001 19:01:45 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime:	16 Dec 2001 08:01:36.0982 (UTC) FILETIME=[E2BA0760:01C18607]

----- Original Message -----
From: "Jason Tishler" <jason AT tishler DOT net>


> Rob,
>
> On Mon, Dec 10, 2001 at 11:42:01PM +1100, Robert Collins wrote:
> > Possibly because the cygwin heap is getting allocated across where
those
> > .dll's would go.
>
> That is what I figured.  Any suggestions on a good address to use
during
> the rebasing?

Leave ~ the size of the cygwin heap between each .dll needed to load
bash + (say) vim. Then use process explorer to see where the heap is
occuring, and rebase everything second time avoiding that base + the
size of the maximum heap.

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/

- Raw text -