public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Werner Tuchan" <tuwn@gmx.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
Date: Fri, 21 Dec 2001 06:46:00 -0000 [thread overview]
Message-ID: <20011221144602.20399.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/5149; it has been noted by GNATS.
From: "Werner Tuchan" <tuwn@gmx.net>
To: "Neil Booth" <neil@daikokuya.demon.co.uk>
Cc: <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: 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.
next reply other threads:[~2001-12-21 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 6:46 Werner Tuchan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 4:26 neil
2001-12-21 23:36 Zack Weinberg
2001-12-21 10:56 Neil Booth
2001-12-21 9:26 Christopher Faylor
2001-12-20 11:16 Neil Booth
2001-12-20 11:06 Zack Weinberg
2001-12-20 10:36 Neil Booth
2001-12-20 6:46 Werner Tuchan
2001-12-19 16:20 neil
2001-12-18 3:56 tuwn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011221144602.20399.qmail@sources.redhat.com \
--to=tuwn@gmx.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).