multipipe problems

New Message Reply Date view Thread view Subject view Author view

Cynthia H. Ferguson (chf++at++netcom.com)
Mon, 21 Nov 1994 12:28:39 -0800

I am having problems getting a multipiped application running.
I am using GLX windows inside an X/Motif application. When
I use the following :
        pfMultipipe(1);
        pfMultiprocess(PFMP_APPCULLDRAW);
two processes are created and my program continues executing
correctly. When I use :
        pfMultipipe(2);
        pfMultiprocess(PFMP_APPCULLDRAW);
six (yes, 6) processes are created. My main process sits in
pfSync waiting for something and the active process (the one
accumulating the time) is in pfConfig doing an mpDraw. The
other four processes are sitting in pfConfig waiting for something.
This happens on both an Indigo2 and a 2 processor Onyx. I have
sample code which causes this and I have the call stacks for all
6 processes.

Other bits of perhaps useful information : I patterned my app after
Wade Olsen's Motif example posted on this list. I did try using
pfuGLXWinopen and the same behavior occured (I didn't get call
stacks from that execution). I am using an Xt work proc to do
my drawing but I thought that X11/Motif did not do any multiprocessing.
I am using XtAppMainLoop for my event handling.

Any tips, suggestions for how to get this working would be appreciated.
I don't understand why I get multiple processes when I specifically
set the mode to only one process.

Thanks,
Cindy
Talisman Dynamics, Inc.

PS. Here is the call stack for my main process :
_ioctl() ["ioctl.s":15]
_usblock() ["usemas.c":1109]
_Psema(<stripped>) ["usemas.c":136]
pfSync() ["pfProcess.C":1371]
PerformerWidget::draw_workproc(data=0x1004a138) ["performerWidget.c++":180]
CallWorkProc(<stripped>) ["NextEvent.c":673]
XtAppNextEvent() ["NextEvent.c":737]
XtAppMainLoop(<stripped>) ["Event.c":1200]
main(argc=1, argv=0x7fffaf34) ["main.c++":104]
__start() ["crt1text.s":133]

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:40 PDT

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