Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 22 Nov 2000 12:31:44 -0800
From:	"Zack Weinberg" <zackw AT Stanford DOT EDU>
To:	Chris Abbey <cabbey AT bresnanlink DOT net>
Cc:	Kelley Cook <Kelley DOT Cook AT home DOT com>,
	"GCC-Bugs AT gcc DOT gnu DOT org" <GCC-Bugs AT gcc DOT gnu DOT org>,
	"GCC-patches AT gcc DOT gnu DOT org" <GCC-patches AT gcc DOT gnu DOT org>,
	Cygwin mailing list <Cygwin AT sources DOT redhat DOT com>
Subject:	Re: Reason for cygwin GCC 2.97 non-bootstrap found
Message-ID:	<20001122123143.G820@wolery.stanford.edu>
References:	<20001121195005 DOT A17637 AT disaster DOT jaj DOT com> <200011211839 DOT eALIdOd15553 AT ahmlir2 DOT mail DOT eds DOT com> <20001121162522 DOT G17712 AT wolery DOT stanford DOT edu> <20001121195005 DOT A17637 AT disaster DOT jaj DOT com> <20001121171653 DOT I17712 AT wolery DOT stanford DOT edu> <5 DOT 0 DOT 0 DOT 25 DOT 0 DOT 20001121195807 DOT 02cc7040 AT pop DOT bresnanlink DOT net>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<5.0.0.25.0.20001121195807.02cc7040@pop.bresnanlink.net>; from cabbey@bresnanlink.net on Tue, Nov 21, 2000 at 08:04:19PM -0600

On Tue, Nov 21, 2000 at 08:04:19PM -0600, Chris Abbey wrote:
> At 17:16 11/21/00 -0800, Zack Weinberg wrote:
> >Uh oh, that means I don't understand what's going on.  Can you try
> >this augmented version of the test program, which probes things a bit
> >more thoroughly?  Now I want the output and the exit status.  [If you
> >know how, also try to turn on Cygwin's internal debug logging and tell
> >me what that reports.]
> >
> >zw
> 
> hth...

...
> mmap: error 0
> munmap: Invalid argument
> signal: error 0

Ah.  So we aren't actually unmapping anything when this happens.  I
could imagine the code getting confused and crashing because of that;
in any case, we're wasting tons of memory this way - it also means
that the "unmap huge chunk of memory all at once" trick won't work.

RTH is right, we shouldn't be pretending cygwin has anonymous mmap.
I'll see if I can't turn the test program into an improvement to the
autoconf test.

zw

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -