Re: [boost] [interprocess] Different processes accessing shared memory in different locations

Subject: Re: [boost] [interprocess] Different processes accessing shared memory in different locations
From: Gavin Lambert (gavinl_at_[hidden])
Date: 2013-09-10 19:44:40

On 10/09/2013 10:01 p.m., Quoth Tom Sanham:
> Our application has the following scenario using Boost V1.0.52:
>
> 1) Process A writes to boost interprocess shared memory. The files
> appear at
> C:\ProgramData\boost_interprocess\...

This doesn't really address your issue, but something that puzzles me 
about this report is: why are files being used for shared memory at all?

I'm not really familiar with Interprocess so maybe I'm missing something 
fundamental, but I can't think of any good reason to use an on-disk file 
if you just want some IPC shared memory.  (It would be useful only if 
you want persistent storage in case the two processes are not actually 
running at the same time, which seems like a very unusual scenario for IPC.)

(And there are permissions issues with accessing files in CommonAppData, 
which could explain the OP's problem if the library doesn't address them.)