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: Wed, 3 Sep 2003 09:20:29 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: malloc segfaults Message-ID: <20030903132029.GA9575@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3F549C88.9040103@osc-es.de> <017f01c37193$f4c9c160$c900000a@docbill002> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <017f01c37193$f4c9c160$c900000a@docbill002> User-Agent: Mutt/1.4.1i On Tue, Sep 02, 2003 at 04:50:40PM -0400, Bill C. Riemers wrote: >Definitely looks like a cygwin1.dll bug to me. I see consistently the >traceback either terminates in >strdup() called from mmap64(), or mktime() called from strdup(). Do you see a strdup anywhere in mmap64 or a call to mktime() (?) from strdup? I don't. That would indicate that your traceback is highly suspect. cgf -- 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/