This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin

From: "Werner Tuchan" <tuwn at gmx dot net>
To: "Neil Booth" <neil at daikokuya dot demon dot co dot uk>
Cc: <neil at gcc dot gnu dot org>,<gcc-bugs at gcc dot gnu dot org>,<gcc-gnats at gcc dot gnu dot org>
Date: Fri, 21 Dec 2001 15:42:14 +0100
Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
References: <20011220002004.23509.qmail@sources.redhat.com> <000701c18964$fad2d2e0$fb4d0ed4@softron.de> <20011220183323.B3065@daikokuya.demon.co.uk>

>
> Weird.  The bytes after EOF are a mixture of NULs and 0xc0.  Is 0xc0
> of special significance in Windows?  Is your version of cygwin the
> latest?  I recall some talk about mmap bugs in cygwin.
>

The cygwin version is pretty recent. Two weeks old or so. The data after EOF
is only garbage. I've seen different values than 0x0 or 0xc0 in the error
messages. Windows propably doesn't clear the page before mapping the file
onto it. There is likely a different behaviour here between Windows ME and
NT.

Follow-Ups:
- Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
  - From: Christopher Faylor

References:
- Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
  - From: neil
- Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
  - From: Werner Tuchan
- Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
  - From: Neil Booth

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]