Re: shared memory segment

New Message	Reply	Date view	Thread view	Subject view	Author view

Jim Helman (jimh++at++surreal)
Sat, 18 Feb 95 18:21:51 -0800

Next message: Jim Helman: "Re: shared memory segment"
Previous message: Jim Helman: "Re: My discFunc has dumped and it can't get up..."
In reply to: Andy Mirkis: "My discFunc has dumped and it can't get up..."
Next in thread: Robert Keller: "Re: shared memory segment"
Reply: Robert Keller: "Re: shared memory segment"

> 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.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

Next message: Jim Helman: "Re: shared memory segment"
Previous message: Jim Helman: "Re: My discFunc has dumped and it can't get up..."
In reply to: Andy Mirkis: "My discFunc has dumped and it can't get up..."
Next in thread: Robert Keller: "Re: shared memory segment"
Reply: Robert Keller: "Re: shared memory segment"

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.