X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.4 required=5.0	tests=AWL,BAYES_00,RCVD_IN_NJABL_PROXY,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT nexgo DOT de>
Subject: Re: emacs and large-address awareness under recent snapshots
Date: Mon, 08 Aug 2011 20:20:28 +0200
Lines: 23
Message-ID: <87sjpbhij7.fsf@Rainer.invalid>
References: <4E3C79E0 DOT 3030506 AT cornell DOT edu>	<20110807113354 DOT GG11601 AT calimero DOT vinschen DOT de>	<20110807115056 DOT GI11601 AT calimero DOT vinschen DOT de>	<4E3EA497 DOT 7040402 AT cornell DOT edu> <4E3EBAEF DOT 1030004 AT cornell DOT edu>	<20110807200222 DOT GK11601 AT calimero DOT vinschen DOT de>	<4E3F13D8 DOT 7090608 AT cornell DOT edu> <4E3FE323 DOT 9020201 AT cornell DOT edu>	<20110808155048 DOT GA28218 AT calimero DOT vinschen DOT de>	<4E40093D DOT 10107 AT cornell DOT edu>	<20110808162556 DOT GM11601 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Corinna Vinschen <...> writes:
> still tries to workaround some old problem in the Cygwin sbrk
> implementation in Cygwin 1.5.  Unfortunately the comment doesn't contain
> any hint as to what exact problem this code is trying to workaround.

Apologies if that's obvious and you've already checked that: emacs gets
created as a dumpfile of temacs during build, so if peflags moves the
heap retroactively thereafter I can't see how it's going to work since
part of the heap is where it was during dumping and the rest is, well,
somewhere else.  I'd look at the build process first before suspecting
the sources — I would assume that temacs must also be made large address
aware and that it right now just isn't.  There may still be workarounds
that aren't needed anymore and bad assumptions about how the memory map
looks like in Cygwin.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


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