Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!osiris.cso.uiuc.edu!gordon
From: gordon@osiris.cso.uiuc.edu (John Gordon)
Newsgroups: comp.sys.sequent
Subject: Re: Shr\"odinger error in _XRead!
Message-ID: <1991Jun3.155918.5087@ux1.cso.uiuc.edu>
Date: 3 Jun 91 15:59:18 GMT
References: <10613@castle.ed.ac.uk>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 13


	I have experienced something like what you described.  We had a program
that would occasionally bomb, but when we put a printf() in a certain spot
to check a value, the error went away.  It turned out that at a certain point
the program was using an uninitialized variable, and the printf call just
happened to leave the correct values in a few key bytes in memory.  Use lint
and check for usage before initialization.


---
John Gordon
Internet: gordon@osiris.cso.uiuc.edu        #include <disclaimer.h>
          gordon@cerl.cecer.army.mil       #include <clever_saying.h>