Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!elroy.jpl.nasa.gov!aero!tak
From: tak@aerospace.aero.org (Michael L. Takayama)
Newsgroups: comp.sys.sgi
Subject: Re: Window Manager Crashes
Message-ID: <65904@aerospace.AERO.ORG>
Date: 1 Feb 90 03:37:44 GMT
References: <13273@phoenix.Princeton.EDU>
Reply-To: tak@aero.UUCP (Michael L. Takayama)
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 33

In article <13273@phoenix.Princeton.EDU> markv@gauss.Princeton.EDU () writes:
>
     ...Stuff deleted...

>After running for a while, the window manager crashes with the following
>message:
>
>-----
>fifo_intr: GM TIMEOUT (FIFO still > half full)!
>
>The window manager was killed by signal 15.
>-----
>

We used to get this problem all of the time in one of our big programs
and, after a lot of headaches, tracked it down to passing double
precision values to the v3f() commands.  Funny thing is that this
*will* work for a random period until enough points have been pushed
down the graphics pipeline - then it croaks with the above-mentioned
*super-informative* error message.

I recommend checking your data types - a *lot* of the GL routines are
not very happy with being passed the wrong data types [Type-checking
in C?  What a concept... :-) ].

We also ran into the NaN problem with n3f().  Very bad stuff with very
useless error messages...

Good luck -

Michael L. Takayama
Computer-Aided Engineering Department
The Aerospace Corporation