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:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=tir
	KY5CHoJZBBOIxvyuD2XHQhT8udnQUFDPi+3B477p1kXPWfjL28gBX/Q2PjNwXb7Q
	0I+QRviX1hv29FfmIupOMSxLztrHaHnClyli9MuILyktDGkOduXHnfqR9IHmuSgQ
	vh6cJRPUTX5NnDqEuGo0VT7PO418sDVjHWrRZDdM=
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:mime-version
	:content-type:content-transfer-encoding; s=default; bh=oHlcIYzHK
	zzF5mB/URPm1424fN8=; b=Q8v27uuuG4sWkJjpUjxDFjYmqB9YbqT1axuaKzk1V
	E6E7XAmLpzcja6Htsr8juKGMdHS6Zqleh5tsS6gn05mtRzbBxRjDvBfl519w74FN
	rzUwTqtTxyqEX5s40yT8yV+3paLGTmTHiAZ8zrMh4HeCqmtI3oFOEv1YZa/vZy+5
	bI=
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=0.1 required=5.0 tests=AWL,BAYES_00,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:	Process map and fork problems
Date:	Wed, 20 Apr 2016 10:27:46 +0000 (UTC)
Lines:	21
Message-ID:	<loom.20160420T121651-786@post.gmane.org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

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.  If I rebase the
colliding DLL manually out of this region, things start to work again.

Is there any way to find out where these come from?  The address range seems
to be fixed so far, so I probably could have rebase skip this range, but I'd
rather move these out of the way if possible.


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

- Raw text -