Tom Impelluso (verdi++at++piano.ucsd.edu)
Sat, 1 Nov 1997 16:35:42 -0800
I have an xforms code (basically, a GUI).
This GUI creates a shared arena for displaying an object.
Then the GUI code forks a number cruncher (FEM) code,
and a Performer Code (PER).
Both PER and FEM first join the arena created by GUI.
Then, PER and FEM go about their business....
However...
As FEM changes the geometry, PER's app() process
notices the change because I am having the while loop
print out the data:
while(!exit) {
pfSync()
pfFrame()
Update()
print data <--- so I know that PER is
correctly reading the new data.
}
However, the drawing never changes.
? ?
In the FEM and PER codes, I call joinArena() which contains calls
for usinit(), usmalloc(), usgetinfo(), etc.
This is the initialization sequence:
/* blah blah */
pfInit()
pfInitUtil()
pfiInit()
pfConfig()
/* blah blah */
So... where in this sequence should PER join the
arena created by GUI -- the arena, which contains the common
data geometry, and which is shared by PER, FEM and GUI?
... where should I call joinArena()?
This is getting to be frustrating, because, originally,
I had GUI sproc() both FEM and PER; however, that produced problems
and I was told NEVER to have a code the size of FEM and PER sharing
the same data space. So I abandoned sproc(),
and am now having GUI fork()-exec()'ing the FEM and PER
However, now I have to make sure they have a common memeory area.
But, it seems I am once again up agains the wall because it seems that
the joinArena() calls (which use IRIX shared memory: usmalloc, usinit,
etc.), is now conflicting with Performers attempt to fork, and create
shared arenas.
HELP!
Tom
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:12 PDT