From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13743 invoked by alias); 20 Dec 2001 19:16:04 -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 13720 invoked by uid 71); 20 Dec 2001 19:16:03 -0000 Date: Thu, 20 Dec 2001 11:16:00 -0000 Message-ID: <20011220191603.13717.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Neil Booth Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Reply-To: Neil Booth X-SW-Source: 2001-12/txt/msg01018.txt.bz2 List-Id: The following reply was made to PR bootstrap/5149; it has been noted by GNATS. From: Neil Booth To: Zack Weinberg Cc: Werner Tuchan , neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Date: Thu, 20 Dec 2001 19:09:10 +0000 Zack Weinberg wrote:- > No. But the AC_FUNC_MMAP_FILE macro (gcc/aclocal.m4) already executes > a test program to determine whether or not mmap works the way we want. > It would be easy enough to add a check that byte (len+1) of its test > file is a NUL. [And we'd better not be looking at byte len+2, or > we'll segfault if the file length is one less than a multiple of > PAGE_SIZE.] Looking at the dump Werner supplied, filled with 0xc0 and NULs, I fear this could pass on cygwin by fluke. Better just to blacklist it IMO. HAVE_BROKEN_MMAP or something. Neil.