How do *you* debug device drivers?

[Chris Torek]

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 at umcp-cs		ARPA:	chris at maryland