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: Neil Booth <neil at daikokuya dot demon dot co dot uk>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Werner Tuchan <tuwn at gmx dot net>, neil at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org,gcc-gnats at gcc dot gnu dot org
Date: Thu, 20 Dec 2001 19:09:10 +0000
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> <20011220185747.GC806@codesourcery.com>

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.

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

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
- Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
  - From: Zack Weinberg

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