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
Reply-To:	<shanem AT citr DOT com DOT au>
From:	"Shane Mann" <shanem AT citr DOT com DOT au>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: cygwin 1.3.3 WinNT4.0 munmap invalid argument - now running 1.3.11(0.53/3/2) 2002-06-23
Date:	Thu, 27 Jun 2002 12:01:18 +1000
Message-ID:	<000001c21d7e$8707b7f0$8e90a8c0@citr.com.au>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
In-Reply-To:	<20020627002259.GA25096@redhat.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner:	Found to be clean

No particular reason, have upgraded now though.

Problem still occurs.

Regards,
Shane

Shane Mann
Software Engineer          Phone: +61-7-3259-2223
CiTR Pty Ltd               Fax:   +61-7-3259-2259
339 Coronation Drive,      Email: shanem AT citr DOT com DOT au
Milton, QLD, 4064          Web:   http://www.citr.com.au


> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Christopher Faylor
> Sent: Thursday, 27 June 2002 10:23
> To: cygwin AT cygwin DOT com
> Subject: Re: cygwin 1.3.3 WinNT4.0 munmap invalid argument
>
>
> 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/
>


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