Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!mips!sgi!davea@quasar.wpd.sgi.com
From: davea@quasar.wpd.sgi.com (David B.Anderson)
Newsgroups: comp.sys.sgi
Subject: Re: More /tmp woes (with ugen)
Message-ID: <108331@sgi.sgi.com>
Date: 5 Jun 91 23:38:37 GMT
References: <9106051132.aa28547@VGR.BRL.MIL>
Sender: guest@sgi.sgi.com
Reply-To: davea@quasar.UUCP (David B.Anderson)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 25

In article <9106051132.aa28547@VGR.BRL.MIL> SOFPJF@VM.UOGUELPH.CA (Peter Jaspers-Fayer) writes:
[stuff deleted from various places to shorten the reply]
>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
>A long while later, I finally found in SYSLOG:
>unix: dks0d1s0 (/): Out of space

Two problems with the compiler back-end tools (ugen, as1, uopt):
1) They never report file i/o problems helpfully (as the example above
   demonstrates).
2) Problem reports tend to be a confusing mixture of information
   for the user and for the tool-maintainers.

In 4.0 the ugen messages have been made slightly clearer (in many cases)
but no one had time to do the rather large amount of work that would be
needed to really *fix* the problems.  Sorry.

We will fix these problems in some future release.

[ David B. Anderson  Silicon Graphics  (415)335-1548  davea@sgi.com ]
[``What could possibly go wrong?''                      --Calvin
 `` Whenever you ask that, my tail gets all bushy.''    --Hobbes    ]