Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!orc!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.questions
Subject: Re: How to Deal with Obscure Problems on UNIX
Message-ID: <1990Nov14.181843.18166@chinet.chi.il.us>
Date: 14 Nov 90 18:18:43 GMT
References: <85864@tut.cis.ohio-state.edu> <7220:Nov1408:26:4390@kramden.acf.nyu.edu>
Organization: Chinet - Public Access UNIX
Lines: 20

In article <7220:Nov1408:26:4390@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:

>I make sure that all error messages in my programs are documented.

What about the ones you get back from perror() that you might not
know about when you write the program?  The "not a typewriter"
message that you get from calling perror after a successful stdio
operation to a file is probably the classic, but displaying the
"Multihop attempted" message you might get on a system with RFS
could be equally confusing out of context.

BTW, my all-time favorite error message comes from the AT&T starlan
network listen program.  It displays it on the console and puts it
in the log file as it dies:
  "Software bug -- should not happen"

Yes, it happens... (but only on one of several nearly identical machines).

Les Mikesell
  les@chinet.chi.il.us