From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8b44ecd3f5eb0e47,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-09-16 07:43:26 PST
Path: 
 bga.com!news.sprintlink.net!sundog.tiac.net!usenet.elf.com!news2.near.net!MathWorks.Com!udel!darwin.sura.net!gwu.edu!seas.gwu.edu!ckann
From: ckann@seas.gwu.edu (Charles W. Kann)
Newsgroups: comp.lang.ada
Subject: Debugging anecdotes
Date: 15 Sep 1994 15:53:47 GMT
Organization: George Washington University
Message-ID: <359qmb$70@cronkite.seas.gwu.edu>
NNTP-Posting-Host: 128.164.9.3
X-Newsreader: TIN [version 1.2 PL2]
Date: 1994-09-15T15:53:47+00:00
List-Id: <comp.lang.ada>

I would appreciate any anecdotes describing debugging experiences.  In
particular, I am interested in particularly difficult bugs to find in
large pieces of software which caused you lots of headaches.  I am
particularly interested if the software was written in Ada.  I would
like to know what the problem was, and what caused it. I also want to know
how you went about solving the problem, ie did you home in on the bug
systematically, did the solution come to you in a dream, whatever.  Also, 
what tools did you use in finding the bug.

A brief stream-of-consciousness reply (right now!) would be much better
than a carefully worked out story.  I can get back to you if I need
further details.

Please mail posts to me directly, as otherwise they might devolve into other
threads on the list and I will not be able to track them.  If you can,
use the subject header on this message (Debugging anecdotes) to indentify 
the mail.  Also, if you have friends who program in Ada who do not read
this list but who may be able to contribute to this query, please have
them send their stories to me.

Thanks

--
chuck kann
ckann@seas.gwu.edu