Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Debugging the kernel: proper methods?
Message-ID: <7224@mimsy.UUCP>
Date: Fri, 26-Jun-87 22:43:16 EDT
Article-I.D.: mimsy.7224
Posted: Fri Jun 26 22:43:16 1987
Date-Received: Sat, 27-Jun-87 12:38:17 EDT
References: <2713@uw-june.UUCP> <479@winchester.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 18

In article <479@winchester.UUCP>, djl@mips.UUCP (Dan Levin) writes:
>... I crank up our version of dbx that understands how to debug
>running kernels. ...
 
>In past lives, I have spent a fair amount of time hunched over a hex symbol
>table running a PROM level debugger under a kernel. ...

>A final, and very painful, technique, is to use printf()'s.

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, running-kernel debuggers are handy.  There is one in use
internally at Berkeley.  Look for it someday in a BRL distribution.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seis't g't g'I hax!