Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC830713); site vu44.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!hao!seismo!mcvax!vu44!jack From: jack@vu44.UUCP (Jack Jansen) Newsgroups: net.unix-wizards Subject: How do *you* debug device drivers? Message-ID: <541@vu44.UUCP> Date: Fri, 28-Dec-84 14:57:28 EST Article-I.D.: vu44.541 Posted: Fri Dec 28 14:57:28 1984 Date-Received: Sun, 30-Dec-84 01:57:33 EST Organization: The Retarded Programmers Home, VU, Amsterdam Lines: 18 [A crash a day keeps the users away] After reading the articles about VM/370, I was wondering how the average unix-wizard debugs his/her device driver(or other kernel mods). What I usually do is the most obvious thing: kicking everyone off the system, loading my new unix, (usually) watching it crash, and examining either the remains of it, or the real thing in action. Since this usually involves awful things like printf's on the console and lots of booting, I wondered whether there might be anyone out there who developped a more reasonable way of debugging kernel mods. Waiting for the great and simple solutions, -- Jack Jansen, {seismo|philabs|decvax}!mcvax!vu44!jack or ...!vu44!htsa!jack If *this* is my opinion, I wasn't sober at the time.