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:	Wed, 3 Sep 2003 09:20:29 -0400
From:	Christopher Faylor <cgf-rcm AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: malloc segfaults
Message-ID:	<20030903132029.GA9575@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3F549C88 DOT 9040103 AT osc-es DOT de> <017f01c37193$f4c9c160$c900000a AT docbill002>
Mime-Version:	1.0
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/

- Raw text -