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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=IbkRfqTzaaLhzndE
	EpQpfY/B8OHnhdjhHpTs6UvSOxSicOBEfO5xzATnjuehHuiC3PRShvp04YHk2n+U
	fRSfHEPV2ajV9DMcQ0c5064Bz+qNejLCtw0jXQv5bhuHUbAZ1k0j8847eGkV3hWv
	zyKk6Kcm8g4smAklenjJBFhv++Q=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=q5iLFCz47bYLiUbzFbVf+J
	jr4js=; b=fN3LCWWMF2Bp2DgXwy0OVLlOFZKvmtojix709FR4YqF7fwVBFXiocr
	Uui5d7zSbfg+fY6aIrtTb6wkwqiSS2Y2BuCKAjcP8JyHAJxNUBZ5aPAUB50s13Ph
	FMLkhlTwcpOuTC1Y9QwiElvK+AuW2PzVQgnA3Uw15CwCj9y7PG5UQ=
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.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*R:D*edu
X-HELO:	mailsrv.cs.umass.edu
Reply-To:	moss AT cs DOT umass DOT edu
Subject:	Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating
To:	cygwin AT cygwin DOT com
References:	<CAFWoy7G6qey3krstkgwYpjQYoxMejTF18Ds5B-vcA28OG4gU4A AT mail DOT gmail DOT com> <35eff42d-9022-ddf8-27f6-9a1889544852 AT cornell DOT edu> <CAFWoy7Fbv00KaWv5Yjoxsh4Dwar-S3qH-ma4rt2GU743+k9LBg AT mail DOT gmail DOT com> <CAFWoy7F6cyx02qttLQDhjUeK0gezsP2nPtEwdJ3z6s5fOrW8vQ AT mail DOT gmail DOT com> <CAFWoy7H14=pPmGi0NN5NZZR4u2a0S2dW5-OB9=yq3iiNP3Ebfg AT mail DOT gmail DOT com> <c100f9f7-f722-f1a3-b10a-158b24aa92e4 AT cs DOT umass DOT edu> <7910bbfa-5adf-02ec-39a6-a620180c8695 AT gmail DOT com> <36c2aa01-c5ca-3f6b-e81d-76ec3a2bb2f0 AT cs DOT umass DOT edu> <e7b0c010-9b88-e0e7-c537-c08920d021be AT gmail DOT com>
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<0c22babf-d186-67aa-bc9d-3fa46d35be6c@cs.umass.edu>
Date:	Wed, 30 Aug 2017 10:19:15 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version:	1.0
In-Reply-To:	<e7b0c010-9b88-e0e7-c537-c08920d021be@gmail.com>
X-IsSubscribed:	yes

> you should look if
> - you have collisions ( they are signed by * in rebase -si output)

Good tip

> - if you have very low address as allocation is starting at 0x6fff....
> and going down.

I guess I was asking "What is very low?"  My 32-bit installation
currently goes down to 0x3b960000.

In my 64-bit installation it is 0x0003c3c50000.

Would it not be simple to add something to rebase to have it
point out possibly/probably problematic cases?

Regards - Eliot


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