shared memory segment

New Message	Reply	Date view	Thread view	Subject view	Author view

Lance R. Marrou (marrou++at++vsl.ist.ucf.edu)
Fri, 17 Feb 1995 18:03:58 -0500 (EST)

Next message: Kent Miller: "Class Libs for Performer"
Previous message: Scott A. Friedman: "Question about pfInitGLXgfx 'mode' parameter."
Next in thread: Jim Helman: "Re: shared memory segment"
Reply: Jim Helman: "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.
In the process which runs Performer, however, I use no shared memory segments
(directly). The following are the last four Performer calls executed:

  pfuFreeCPUs();
  pfuExitUtil();
  pfuExitInput();
  pfExit();

Any ideas on what I can do to properly remove this segment?

______________________________________________________________________________
/\ ______ /\____ ______ ______ E-mail: marrou++at++vsl.ist.ucf.edu
Visual / / / _ / / __ // ____// ____/ VSL: (407)658-5073
Systems / /__ / /_/ / / / / // /___ / __/_ R. Marrou Fax: (407)658-5059
Lab /____//____/\\/_/ /_//_____//_____/ http://www.vsl.ist.ucf.edu/~marrou
"Reap the whirlwind." "We don't need no thought control."

Next message: Kent Miller: "Class Libs for Performer"
Previous message: Scott A. Friedman: "Question about pfInitGLXgfx 'mode' parameter."
Next in thread: Jim Helman: "Re: shared memory segment"
Reply: Jim Helman: "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.