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,e4f9827899b0936f,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-12 08:59:02 PST
Newsgroups: comp.lang.ada
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!agate!msuinfo!uchinews!news
From: Charles Fiterman <cef@geodesic.com>
Subject: Looking for a study of program bugs
Message-ID: <1994Oct12.150518.7743@midway.uchicago.edu>
Sender: news@uchinews.uchicago.edu (News System)
Organization: Geodesic Systems
Date: Wed, 12 Oct 1994 15:05:18 GMT
Date: 1994-10-12T15:05:18+00:00
List-Id: <comp.lang.ada>

We are looking for statistical studies on how programs
get bugs. We are especially interested in the following
classifications.

Storage allocation bugs, either memory leaks or premature
freeing.

Indentation syntax mismatch. That is the program is indented
one way but reads another to the parser.
	if (x < 0)
	   a = 1;
	   b = 2;

This is sometimes called the dangling else bug is in.
	if (something)
		if (somethingElse)
			doSomethingElse;
	else
		doSomething;

Missing statement delimeters or terminators. (semicolons)

Uninitialized variables.

Failure to finalize procedures or objects caused by inner
exit or return.


These questions all impact language design.

Please email any responces to
	cef@geodesic.com