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, 26 Jun 2002 20:22:59 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.3.3 WinNT4.0 munmap invalid argument
Message-ID:	<20020627002259.GA25096@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20020626100748 DOT N22705 AT cygbert DOT vinschen DOT de> <001c01c21d6f$774f5b60$8e90a8c0 AT citr DOT com DOT au>
Mime-Version:	1.0
In-Reply-To:	<001c01c21d6f$774f5b60$8e90a8c0@citr.com.au>
User-Agent:	Mutt/1.3.23.1i

On Thu, Jun 27, 2002 at 10:13:30AM +1000, Shane Mann wrote:
>OK - I wasn't sure what the list would be like - after 100+ emails overnight
>I see it is quite active.
>
>I have created a test case - hopefully it's not to hard to follow. I can
>compile and run it under redhat linux with no errors, but not under cygwin.
>There are 2 parts, the c code (munmap_test.c) and a text file
>(cygcheck.out) - as the mapping is using a file descriptor. I thought it may
>be useful to make the text file the output from cygwin configuration
>diagnostics. In both cases gcc with no other options was used to compile.

Just out of curiousity, why are you running 1.3.3 when the current cygwin
revision is 1.3.11?  The first step in debugging a problem like this should
always be to try the newest version.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -