Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!VM.UOGUELPH.CA!SOFPJF
From: SOFPJF@VM.UOGUELPH.CA (Peter Jaspers-Fayer)
Newsgroups: comp.sys.sgi
Subject: More /tmp woes (with ugen)
Message-ID: <9106051132.aa28547@VGR.BRL.MIL>
Date: 5 Jun 91 16:18:14 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Computing Services, University of Guelph, Ont. Can. N1G 2W1
Lines: 30

I know this has already been discussd (with FORTRAN), but after having
sweated this one out for about an hour, I'd like to relate this war story
in case someone else should be so unlucky (and in case someone at SGI
is "listening"):

I have this C program that writes some messy PostScript.  I was testing
it, found a bug, removed a "printf", and attempted to re-compile:

ugen: internal  : line 82 : build.p, line 1740
                unexpected u-code

it sez.  Whattheheckizzat? Say WHAT?  Line 82 is no where near my change.
Quick, put that printf back! To no avail.  In trying to "vi" the .PS file
I spooted this strange error message which started me on the right track.
A long while later, I finally found in SYSLOG:

unix: dks0d1s0 (/): Out of space

Similar messages appeared in my (iconified - tsk) console window.

Seems psview left some crud in /tmp, and so...


1) The above compiler message is not too informative (Hello SGI?)
2) Is there a  way to "open" and "pop" a hidden or iconified
   wsh window whenever there is any output to it?

 /PJ                                __o
                                   -\<,
                             ......O/ O             SofPJF@VM.UoGuelph.Ca