Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Reply-To: From: "Elliot Mednick" To: "Cygwin AT Sourceware. Cygnus. Com" Subject: Re: mmap() for shared memory? Date: Wed, 7 Jun 2000 21:53:13 -0400 Message-ID: <000f01bfd0ec$4e6eb280$0e08a8c0@lexra.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal > Where are you getting the memory from? mmap has to be given something > to map - it doesn't create memory out of thin air. Normally you give > it an open file to map; the only "empty" file is /dev/zero and that's > not shared anyway. Thanks for your response. I'm pretty sure I'm calling mmap correctly. I'm mapping a file and I can see the file being modified afterwards. The problem is that the client side never sees the change. It's almost like there is some disconnect, like the MAP_SHARED parameter didn't "take". There was a posting in January with a similar problem which included an example that worked under real Unix but not under Cygnus; I tried it and couldn't get it to work either with the latest stuff (1.1.2 dll). >> Perhaps someone can suggest the optimal IPC mechanism under Cygwin. > The optimal IPC is, well, IPCs, stuff like shmget(). Unfortunately, > cygwin doesn't support those. I looked at Ludovic Lang's Cygwin IPC package, but it uses mmap, so it doesn't buy me anything (except compatibility with shm). And it uses a daemon, which gets in the way for what I need this for. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com