X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 11 Aug 2011 09:42:43 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: emacs and large-address awareness under recent snapshots
Message-ID:	<20110811074243.GB16868@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20110809082652 DOT GA9492 AT calimero DOT vinschen DOT de> <4E4117AF DOT 3030305 AT cornell DOT edu> <4E414054 DOT 6040206 AT cornell DOT edu> <4E4142F7 DOT 8020708 AT cornell DOT edu> <20110809152155 DOT GB17030 AT calimero DOT vinschen DOT de> <4E417AB6 DOT 5070306 AT cornell DOT edu> <4E41EDE9 DOT 4040004 AT cornell DOT edu> <20110810114716 DOT GA23977 AT calimero DOT vinschen DOT de> <4E42A381 DOT 3080806 AT cornell DOT edu> <4E42AABD DOT 4070107 AT cs DOT umass DOT edu>
MIME-Version:	1.0
In-Reply-To:	<4E42AABD.4070107@cs.umass.edu>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Aug 10 11:58, Eliot Moss wrote:
> On 8/10/2011 11:28 AM, Ken Brown wrote:
> 
> >Would it be possible to accomplish the same goal without using bss_sbrk and the static heap? In
> >other words, can one save the information on the Cygwin heap as part of emacs.exe, so that when
> >emacs is run the heap gets restored? I know virtually nothing about the structure of .exe files and
> >how the loader works, so I have no idea whether that's feasible.
> 
> I would think so.  The trick is knowing what pages contain
> the Cygwin heap.  As for the other approach, these need to
> get dumped as initialized data segments.  It might not be
> too hard if the Cygwin heap provides functions telling you
> where it starts and ends (more generally, the ranges of pages
> in which it lies).
> 
> I begin to wonder, though, whether this would mean having
> to provide two different copies of emacs, one with the
> heap at 0x2... and one with it at 0x8...

Never, please.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -