Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Tue, 9 Sep 2003 10:28:56 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: similar crash in mmap for 1.5.3-1
Message-ID: <20030909082856.GP1859@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3F5D0343 DOT 60300 AT prime-analytics DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F5D0343.60300@prime-analytics.com>
User-Agent: Mutt/1.4.1i

On Mon, Sep 08, 2003 at 03:31:31PM -0700, John Joganic wrote:
> Previous posts described a bug in mmap called via malloc. I am seeing a 
> bug in mmap itself.  The following test does not map large amounts of 
> memory, nor does it leak.  It crashes however, after 4193 (0x1061) 
> iterations every time.  Like the malloc crash, the call stack references 
> strdup, and in this case calloc as well.  On a Linux box, this program 
> runs to completion without a hitch.

This has been fixed a few days ago.  Try a recent snapshot.

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
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/