Path: utzoo!attcan!uunet!snorkelwacker!mit-eddie!bu.edu!bu-cs!dartvax!eleazar.dartmouth.edu!mona
From: mona@eleazar.dartmouth.edu (Mona)
Newsgroups: comp.sys.sgi
Subject: Re: Window Manager Crashes
Message-ID: <19007@dartvax.Dartmouth.EDU>
Date: 1 Feb 90 20:53:56 GMT
References: <13273@phoenix.Princeton.EDU> <65904@aerospace.AERO.ORG>
Sender: news@dartvax.Dartmouth.EDU
Organization: Dartmouth College, Hanover, NH
Lines: 29

In article <65904@aerospace.AERO.ORG> tak@aero.UUCP (Michael L. Takayama) writes:
>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

	Well I have learned this from EXPERIENCE. I had written lots of code andwas integrating them. Everything seemed to work fine when tested seperately. I 
was desperate for a week chasing a bug. I crashed the system a trillion times,
later I discovered that I was calling a library routine without the brackets.
	If you wanna sabotage somebody's code just remove the () from endline,
endpolygon etc and you would be having real fun :-)


>Michael L. Takayama



krish mohan

mona@eleazar.dartmouth.edu