This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
- From: Christopher Faylor <cgf at redhat dot com>
- To: Werner Tuchan <tuwn at gmx dot net>
- Cc: Neil Booth <neil at daikokuya dot demon dot co dot uk>, neil at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org, cygwin at cygwin dot com
- Date: Fri, 21 Dec 2001 12:20:07 -0500
- 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> <002b01c18a2d$aeb7d850$fb4d0ed4@softron.de>
On Fri, Dec 21, 2001 at 03:42:14PM +0100, Werner Tuchan wrote:
>> 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.
Can I ask why we'd be reading beyond EOF? Is it guaranteed that bytes beyond
EOF will be zero on UNIX?
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/