X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 18 Jun 2012 16:51:03 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Windows 8 Release Preview. fork problems with rsync
Message-ID: <20120618145103.GA26243@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAOLRrpGi-OaejySZ82AVDVzt01mPd0A6gWgjaN60W-sqHZG8cw AT mail DOT gmail DOT com> <20120606123434 DOT GA27662 AT calimero DOT vinschen DOT de> <CAOLRrpHQV2JcaK_f1UAEFR33ga=w8hqdNUSEqfZj1ygKXMCVoA AT mail DOT gmail DOT com> <20120606161217 DOT GB30795 AT calimero DOT vinschen DOT de> <CADSoG1tvx3dPMAZ8-CppoEemqU8ObDuj+4JySTGgSvK-LSYkUg AT mail DOT gmail DOT com> <20120606182929 DOT GD30795 AT calimero DOT vinschen DOT de> <4FD06267 DOT 4040204 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4FD06267.4040204@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Jun  7 10:12, Noel Grandin wrote:
> 
> 
> On 2012-06-06 20:29, Corinna Vinschen wrote:
> 
> >On Jun  6 17:59, Nick Lowe wrote:
> >>>Thanks.  I can confirm the effect.  For no apparent reason, the OS
> >>>reserves a 1 Megs shared memory region, top-down allocated, of which it
> >>>uses about 20K.  It's not the PEB or one of the TEBs, though.  Nor is
> >>>it a thread stack.  I checked, and it turns out that it's allocated
> >>>in every process, on 32 and 64 bit systems.  That's kind of worrying
> >>>since that's bound to collide with mmaped regions and pthread stacks a
> >>>lot.  I don't know what to do at this point.
> >
> 
> 
> 
> I assume you've seem the VMMap tool?
> http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx

Yes, and I also know how to use /proc/$PID/maps to get a memory map
of a process.  It's not a problem to see the used memory slot.  The
problem is that it exists at all.  There's no such thing on pre-W8
systems.  Only the PEB and the TEBs are allocated top-down and they
usually don't collide.


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