Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 6 Nov 2001 14:05:22 +0100 From: Corinna Vinschen To: cygwin Subject: Re: 1.1.3: mmap() returns unusable memory segments: segm fault Message-ID: <20011106140522.H2965@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <20011106114642 DOT D2965 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from lothar@concept.de on Tue, Nov 06, 2001 at 01:20:30PM +0100 On Tue, Nov 06, 2001 at 01:20:30PM +0100, Lothar Linhard wrote: > Hi Corinna, > > thanks, I've installed 1.3.4-2 and can verify that the problem > is fixed. I'm still enthusiastic about your response time. > > However, here is another problem I have detected: > > UNIX allows to do one unmap on memory space mapped by > several continous mmaps. Cygwin's munmap doesnt. I can It does as long as either the mapped object is a real file or in case of anonymous mapping the mapped mem space consists of fractions of 64K. In your example, the mem space is just too big to allow that behaviour in the current implementation. It's probably possible to get your testcase working as well. The mem objects are maintained in a linked list. The whole stuff is in mmap.cc in the cygwin sources. Feel free to send a patch. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/