Xref: utzoo comp.lang.c:40067 comp.software-eng:5972
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!ukma!usenet.ins.cwru.edu!abvax!iccgcc.decnet.ab.com!kambic
From: kambic@iccgcc.decnet.ab.com (George X. Kambic, Allen-Bradley Inc.)
Newsgroups: comp.lang.c,comp.software-eng
Subject: Re: Most likely cause of symptoms
Message-ID: <1991Jun13.172407.4858@iccgcc.decnet.ab.com>
Date: 13 Jun 91 22:24:07 GMT
References: <1991Jun6.135234.18165@auto-trol.com>
Lines: 21

In article <1991Jun6.135234.18165@auto-trol.com>, alesha@auto-trol.com (Alec Sharp) writes:
> 
> I'm trying to put together a list of symptoms, and their most likely
> causes, to help people who are trying to debug problems.  This such
> as:
> 
> Intermittent, non-reproducible problems: often memory or timing 
> dependent.  Memory problems often caused by uninitialized variables.
> 
> Bugs that can't be reproduced in the debugger: often memory or timing
> dependent.
> 
> Access violation/exception conditions:  Uninitialized variables,
> arrays out of bounds, pointers out of range.
> 
> Does anyone have other hints they use when debugging?

Try reading Myers or Beizer

GXKambic
standard disclaimer