Re: shared memory segment

New Message Reply Date view Thread view Subject view Author view

Robert Keller (rck++at++fangio)
Sat, 18 Feb 1995 21:35:57 -0800 (PST)

Jim Helman writes:
> > Somewhere in Performer a shared memory segment with the key 0x9a4 is
> > created, but (in my program) never released. I use a few other segments,
> > semaphores, and other things, but everything is removed/erased correctly.
>
> I'd never noticed this before, since Performer does not use shmget.
>
> But winopen() is creating a shared memory segment with that key.
> Neither winclose() nor gexit() seems to remove it.

Yes, this is expected. IrisGL creates, and keeps around a shared
memory segment for several things but most notably for common colourmap
information. Because of IrisGL's lineage and repetoire of traits and
peculiarities, the shared memory segment aids in the communication
of internal IrisGL state between IrisGL program. For those with source,
check out VENICE/gl/gshm.h (also in other architectures) for an idea
what lives in there.

The very first GL program creates it, the rest simply know where
to find it. It probably lives until the machine is rebooted.

...robert

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:58 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.