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=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,78a1af350f4cf4b
X-Google-Attributes: gid103376,public
From: Ted Dennison <dennison@telepath.com>
Subject: Re: Win2000 has 63,000 'defects'
Date: 2000/03/07
Message-ID: <8a3635$oas$1@nnrp1.deja.com>#1/1
X-Deja-AN: 594272822
References: <38A989B7.2D4D6B56@maths.unine.ch>
 <t7u2ja5lpx.fsf@calumny.jyacc.com> <2000Feb15.143333.1@eisner>
 <t7r9ee5ihu.fsf@calumny.jyacc.com> <2000Feb15.155800.1@eisner>
 <t7itzqcdw2.fsf@calumny.jyacc.com> <150220001931201946%emery@grebyn.com>
 <88hbpp$j4i$1@news.btv.ibm.com> <88ma3c$p6a$1@nnrp1.deja.com>
 <2000Feb21.071938.1@eisner> <38C09E9F.2C752521@earthlink.net>
 <38C3D03D.FD5D39D1@earthlink.net> <8a1g93$ijs$1@nnrp1.deja.com>
X-Http-Proxy: 1.0 x39.deja.com:80 (Squid/1.1.22) for client 204.48.27.130
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Tue Mar 07 15:09:29 2000 GMT
X-MyDeja-Info: XMYDJUIDtedennison
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; I)
Date: 2000-03-07T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <8a1g93$ijs$1@nnrp1.deja.com>,
  Robert Dewar <robert_dewar@my-deja.com> wrote:
> In article <38C3D03D.FD5D39D1@earthlink.net>,
>   Charles Hixson <charleshixsn@earthlink.net> wrote:
> > But one still needs debugging tools.
>
> Actually a lot of Ada programmers find that all they really
> need is a good symbolic back trace, and many people use a
> debugger only to obtain this information.

If the only bug under consideration is one that causes an exception, I
could see that. But I fail to see how that helps at all when the bug is
a behavioral or timing issue. Its true that the source of behavioral
bugs can usually be intuited by someone clever who knows all the code
involved intimately and takes the time to think it through. But in a
large project often there is just too much code involved for one person
to grok it all.

As for timing bugs (eg: this routine has 8ms to run, but takes 22),
trying to fix the problem without first using tools to locate it is a
damn good way to waste a lot of time and make a big mess.

As for me, give me all the tools available, and then some. Stack traces,
debuggers, profilers, timers, cpu monitors, data monitors. Love 'em all.

--
T.E.D.

http://www.telepath.com/~dennison/Ted/TED.html


Sent via Deja.com http://www.deja.com/
Before you buy.