Date: Mon, 26 Jul 1999 21:35:54 +0200
To: pgcc AT delorie DOT com
Cc: gordon AT Aptech DOT com
Subject: Re: mmap
Message-ID: <19990726213553.D1938@cerebro.laendle>
Mail-Followup-To: pgcc AT delorie DOT com, gordon AT Aptech DOT com
References: <199907261616 DOT JAA00693 AT boaz DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <199907261616.JAA00693@boaz.com>; from Gordon K. Stone on Mon, Jul 26, 1999 at 09:16:42AM -0700
X-Operating-System: Linux version 2.2.10 (root AT cerebro) (gcc driver version egcs-2.91.66 19990314 (egcs-1.1.2 release) executing gcc version 2.7.2.3) 
From: Marc Lehmann <pcg AT goof DOT com>
Reply-To: pgcc AT delorie DOT com
X-Mailing-List: pgcc AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Mon, Jul 26, 1999 at 09:16:42AM -0700, Gordon K. Stone wrote:
> I have a program in which a number of executables use an mmap'ed file
> to share memory. This used to work fine, but we updated to Redhat ver
> 5.2, and now the changes made by one process are no longer seen by the
> others.

And how does this relate to this mailinglist????????

> I am using the MAP_FIXED flag--the mmap'ed memory contains absolute
> pointers.

Very bad idea, no wonder it breaks ;)

--  
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |