Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!hao!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix-wizards Subject: Re: How do *you* debug device drivers? Message-ID: <2205@umcp-cs.UUCP> Date: Wed, 2-Jan-85 09:28:42 EST Article-I.D.: umcp-cs.2205 Posted: Wed Jan 2 09:28:42 1985 Date-Received: Fri, 4-Jan-85 04:46:18 EST References: <541@vu44.UUCP> <895@dual.UUCP> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 16 Well, the ideal way is not to write any bugs. Of course, we sometimes tend to fall short of the ideal. I like to see where the machine crashed or what the erroneous behaviour was, think a while, and come up with something that explains the problem exactly, without "explaining" things that didn't happen. Then it's time to look at the code and see whether that explanation is correct. If all goes well, this takes only a few minutes, after which we get to observe the *next* crash . . . :-) -- (This line accidently left nonblank.) In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690 UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland