public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John Hughes" <john@Calva.COM>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: RE: bootstrap/3163
Date: Thu, 14 Jun 2001 00:36:00 -0000	[thread overview]
Message-ID: <20010614073601.10643.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR bootstrap/3163; it has been noted by GNATS.

From: "John Hughes" <john@Calva.COM>
To: "Robert Lipe" <robertlipe@usa.net>, <gcc-gnats@gcc.gnu.org>,
   <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>
Cc:  
Subject: RE: bootstrap/3163
Date: Thu, 14 Jun 2001 09:28:32 +0200

 >> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3163&database=gcc
 >> No OS has yet been observed to be so perverse as to leave unmapped
 >> space between consecutive calls to mmap. */
 >>
 >> Well, UnixWare 7.1.1 is that perverse system. It seems to leave
 >> one page between each mapping.
 
 > This is actually documented behaviour.   From the mmap man page:
 >
 >   References to pages in a mapped region which are beyond the
 >   page containing the end of a file will result in the delivery of a
 >   SIGBUS signal.
 
 No, that paragraph says that if I mmap 10 pages from a 5 page file
 access to the 5 pages beyond eof get a SIGBUS (note: not SIGSEGV).
 
 It says nothing about memory OUTSIDE the mmaped region.
 


             reply	other threads:[~2001-06-14  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14  0:36 John Hughes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-13 20:36 bootstrap/3163 Zack Weinberg
2001-06-13  9:46 bootstrap/3163 Robert Lipe

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=20010614073601.10643.qmail@sourceware.cygnus.com \
    --to=john@calva.com \
    --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).