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
