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
Subject:	Re: It's a snapshot
In-Reply-To:	<20030822075537.GB32665@cygbert.vinschen.de> from Corinna Vinschen
	at "Aug 22, 2003 09:55:37 am"
To:	cygwin AT cygwin DOT com
Date:	Fri, 22 Aug 2003 06:17:40 -0400 (EDT)
MIME-Version:	1.0
Message-Id:	<E19q8zE-0005U2-00@russ.local>
From:	"Russell O'Connor" <roconnor AT TheWorld DOT com>

Corinna Vinschen writes:
> 
> > Btw, I know that Corinna has at least one mmap patch to add before this
> > goes gold.
> 
> It's a border case.  I don't know if it's worth to wait for the fix.
> It would be nice if I could reproduce it under a debugger :-(
> 

If you are referring to "malloc returns overlapping buffers", I was
able to get it to fail under the debugger by increasing the malloc
size in the test case from 8000 to 16000.  It then segfaults instead
of returning overlapping buffers, but that's presumably a bug too, and
likely a different manifestation of the same bug.

I know that the stack trace for that case in my original post was not
too useful because there was no debugging information in the cygwin
dll, but I've since built cygwin from CVS and gotten a proper stack
trace.  Unfortunately, it's at work and I won't be back there till
Monday.  But if it would be useful to you I'll make an extra trip in.

Russ

-- 
Russell O'Connor
roconnor AT hsc DOT usf DOT edu

--
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 -