first bug you ever found on an SGI?

[corn]

In my continuing--and no doubt ultimately doomed--attempt to have
the comp.sys.sgi boards a little bit of life in them, I now ask:

what was the first bug you ever found on an SGI?

It could be in IRIX, a SGI program, or a third-party program. Even
something dumb you did writing your own code is fine!

The first bug I remember finding on an SGI was on a Challenge XL.
I was working on a program first written in ALGOL IIRC, and
converted to IBM S/360 FORTRAN 66. I was tasked with merging
with with John Pople's FORTRAN IV CNINDO program (QCPE #395).
Actually, this was much worse than it sounds.

Anyway, I can not remember the first bug I found of the many,
but I do remember the biggest: one program handled everything
as columns, and the other handled the same information via rows.
They had shuffled the punch card print out (I told you it would
get worse!) of CNINDO to make it work as input for the other
program, but never made that change-over via code when they tried
to pass the arrays between the two merged programs.

--
One of my worst nightmares is to have a perfect fortran compiler without
the graphics performance to make use of it.
-- XBR2...@DDATHD21.BITNET / comp.sys.sgi / 23 Oct 88

[Richard]

[Please do not mail me a copy of your followup]

1988, Not a bug per se, but I remember being very much frustrated by the
NeWS approach to UI. It was very difficult to develop, with little to
no documentation on how to use their existing framework, and there was
zero debugging support, so you had to resort to printf style
debugging. It may have been a more elegant design than X10/X11, but
all that elegance doesn't do you any good if you end up being less
productive as a developer.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

Legalize Adulthood! <http://legalizeadulthood.wordpress.com>