X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=pLOjQ/WWrrzhb6UMwdHF4wsbKAL4Cqb2GaWX+vla0uXD6ueCoFllj
	wDsMC2iG4FMIBbdF/mMyHTJcIXuxmGvIIFzDNx1FBP6jYrXhY/5TKSA1iWe4b4Wl
	tDo7ZBEIqIRyFM9Eas4Q5BZT6rPq3ImhiM9YOgtSmDFLBLs48BoNic=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=yNlJG+sikJ7/mJU0Zjp7syTsO6I=; b=hCmuPqS9p4ZreQlxLCJzFG/Jzrrd
	nsTFDjGD5m0+Wq5M4o11Vx4ZTLLwrHVwMoxOyVcjJNYZ7U80+P+DI9fs6qnk0QTa
	Ci7ln5A+Km2woz1FGTvolPi3S7pp3xC1vXI5I5LwEVOApyFuVtsK7bQt6tgtqLpS
	OvjWjBgB7VXUX+w=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.4 required=5.0 tests=AWL,BAYES_50,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=installations, installs, dab, rwp
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT NexGo DOT DE>
Subject: Re: Process map and fork problems
Date: Wed, 20 Apr 2016 10:37:59 +0000 (UTC)
Lines: 24
Message-ID: <loom.20160420T123241-864@post.gmane.org>
References: <loom DOT 20160420T121651-786 AT post DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> I'm chasing a problem on some 32bit Windows installs that supposedly
> happened after one of the Windows updates (and probably other software
> updates) in the last few months (the affected users were unable to pin it
> down further unfortunately).  It's obviously caused by two heap sections in
> the process map that are smack dab in the middle of the address range used
> by rebase:
> 
> 20000000-200A0000 rw-p 00000000 0000:0000 0                   [heap]
> 200A0000-38000000 ===p 000A0000 0000:0000 0                   [heap]
> 
> These do not exist on 32bit Cygwin installs on 64bit Windows installations,
> so I couldn't see these problems on my test machine.

On the 64bit Windows installations two eerily similar heap sections appear
much higher in the process image:

80000000-80070000 rw-p 00000000 0000:0000 0                   [heap]
80070000-98000000 ===p 00070000 0000:0000 0                   [heap]

Hm....  why would something like that move from 2GB down to 0.5GB?

Regards,
Achim.


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