I'm evaluating an off-the-shelf application that requires being run
from a privileged account so it can access a shared memory segment in
an other system. The claim is that it only reads from this shared
memory, but does not write to it (writes to it would corrupt data in
the other system).
The privileged account has read-write permission on the shared memory
segment.

Is there a way to verify while this app is running that it did indeed
attach to the shared memory
segment with a read only flag, as claimed by the vendor? I only know
about commands that look at
the SM segment permissions, not the properties of actual mappings of
the segment to particular
processes address spaces.

Thanks,

Joseph