From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20414 invoked by alias); 21 Dec 2001 14:46:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 20400 invoked by uid 71); 21 Dec 2001 14:46:02 -0000 Date: Fri, 21 Dec 2001 06:46:00 -0000 Message-ID: <20011221144602.20399.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Werner Tuchan" Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Reply-To: "Werner Tuchan" X-SW-Source: 2001-12/txt/msg01035.txt.bz2 List-Id: The following reply was made to PR bootstrap/5149; it has been noted by GNATS. From: "Werner Tuchan" To: "Neil Booth" Cc: , , Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Date: Fri, 21 Dec 2001 15:42:14 +0100 > > 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.