Fischler (src++at++rose)
Wed, 14 Jun 1995 02:58:33 -0700
If you are going to have X drawing to the same graphics pipeline as
your performer display, then you should keep the two from colliding
with your own internal flags or semaphores. There are X calls to do this
but they are quite heavy-handed and also have a lot of additional latency
because they must go through the X server.
If you are using X for just input management, then you don't need to
worry about graphics pipeline collision with the draw.
You should have the input management running in an asynchronous process
from the app and the draw and running on a non-real-time CPU (not the
same CPU as the draw).
->
->----> Statistics display
->
->Here is some more information on my statistics display problems.
->
->I use Performer 1.2 (I dont know want the MR stands for, but in the
->release notes of our Performer installation the product version code
->is said to be SC4-PERF-1.2).
->
->If I understand well, the easiest way to put up a statistics display
->is just call pfDrawChanStats(). If I do this, without modifying
->statistics class/mode enable settings, or channel statistics draw
->modes, the system crashes with a core dump. DBX tells me:
->
-
I too would like to know is causing your stats problem!
Thank you for the stack trace, but
unfortunately, it doesn't seem to yield any more clues.
Did you say you only had trouble when using GLX? That is also
odd. Any chance you can dump your stats code into
pguide/libpfutil/progs/utilui.c and see if you can make that dump core?
That program lets you choose GL/GLX with a command-line option.
src.
--
-----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Graphics Dev.
src++at++sgi.com (415) 390 - 1002 FAX: (415) 965 - 2658 MS 8U-590
-----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:35 PDT