Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!ames!oliveb!felix!zemon
From: zemon@felix.UUCP (Art Zemon)
Newsgroups: comp.unix.wizards
Subject: Re: Debugging the kernel: proper methods?
Message-ID: <3168@felix.UUCP>
Date: Thu, 2-Jul-87 15:21:05 EDT
Article-I.D.: felix.3168
Posted: Thu Jul  2 15:21:05 1987
Date-Received: Sat, 4-Jul-87 13:28:12 EDT
References: <2713@uw-june.UUCP> <479@winchester.UUCP> <7224@mimsy.UUCP>
Sender: daemon@felix.UUCP
Reply-To: zemon@felix.UUCP (Art Zemon)
Organization: FileNet Corp., Costa Mesa, CA
Lines: 20

In article <7224@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>
>Funny, I usually use the old-fashioned technique:  I look at the
>code and see why it did what it did, and recode it to do what it
>should have done. :-)

Actually this isn't so far fetched.  We are all going to
spend X amount of time writing a program.  Now we can either
spend a little time writing it and a bunch of time debugging
it or we can spend all of time writing it correctly the
first time and no time debugging it.  Since the choice is
ours, we obviously prefer debugging to writing!

Of course *I* only spend time debugging so the rest of you
mortals won't feel inferior....  :-)
--
	-- Art Zemon
	   FileNet Corporation
	   Costa Mesa, California
	   ...!hplabs!felix!zemon