🚀 go-pugleaf

In article <1992Aug28.152114.4350@convex.com> peters@convex.COM (James Peters) writes:
>>In article <1992Aug27.185940.8014@menudo.uh.edu> hsingh@Turing.chem.uh.edu (Harpreet Singh) writes:
>>>	I am getting the following message with a module of mine. If
>>>someone has some idea it would be pretty helpful
>>>
>>>!tg_cbnewin 0x2000004 0x7fdfce44 0x2000004 0x7fdfcdfc 0x63746f72
>>>!tg_cbnewin 0x2000004 0x7fdfd614 0x2000004 0x7fdfd5cc 0x1d5a3634
>>>Fatal server bug!
>>>Fatal server bug!
>>>tigr fatal error:tigr fatal error:
>>>My_module: tcp_read failed.
>>>tcp_read: No such device or address
>>>
>>per harpreet this is coming from a stardent/kpc titan p2 workstation.
>>the version of avs is 4.0.
>>

Well, all I can tell you about it is that "tigr" is a name I've seen
in reference to the Titan's framebuffer, so my guess would be you've
stumbled on some rather next bug in their X server implementation on
that hardware.  The tcp_read stuff is what you get when modules and/or
the avs kernel start dying badly.

You really should give us more information if you want us to help.

Have you run your module using avs_dbx and stepped through it?  What
does your module do?  Does AVS continue to function after you get 
these error messages or does the whole process go down?  More details,
please...


-- 

-->  Michael B. Johnson
-->  MIT Media Lab      --  Computer Graphics & Animation Group
-->  (617) 253-0663     --  wave@media-lab.media.mit.edu