On Jan 18 11:57, Christopher Faylor wrote: > 1.5.19 may have aggravated this problem since Corinna's changes to mmap > now use VirtualAlloc'ed space for privately mmapped areas. For some > inexplicable reason, this causes more of this type of collision. I > would swear that once a program uses a memory area in a parent, windows > is much more likely to use that memory for system-like things in the > "forked/execed" child.
Maybe we should use mmap from malloc only for bigger areas again. Not that I like the idea, but if it helps to lower the collisions... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/