Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 9 Sep 2003 10:28:56 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: similar crash in mmap for 1.5.3-1 Message-ID: <20030909082856.GP1859@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3F5D0343.60300@prime-analytics.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@cygwin.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/