Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site osu-eddie.UUCP Path: utzoo!watmath!clyde!cbosgd!osu-eddie!karl From: karl@osu-eddie.UUCP (Karl Kleinpaste) Newsgroups: net.unix-wizards Subject: Re: How do *you* debug device drivers? Message-ID: <28@osu-eddie.UUCP> Date: Thu, 3-Jan-85 23:01:11 EST Article-I.D.: osu-eddi.28 Posted: Thu Jan 3 23:01:11 1985 Date-Received: Fri, 4-Jan-85 05:18:32 EST References: <541@vu44.UUCP> <317@rlgvax.UUCP> Organization: You really don't want to know Lines: 22 ---------- >If you look at the source to the 4.2BSD "adb" (and, I believe, the S3 and >S5 "adb") for the VAX, there is an EDDT #ifdef that seems to be part of >somebody's effort to make a version of "adb" that can be linked or loaded >with a kernel and used on it. ---Guy Harris of Computer Consoles, Inc ---------- Yes, and CCI's own PERPOS operating system (derivative of Unix OS [System ?3?5? don't know which any more]) has this rather neat facility called "ebug" which is a primitive form of adb compiled right into things. It is without a doubt one of the better tools available for debugging that OS. I was really glad I had it available to me when I was working there. Now, it is quite primitive, allowing only absolute addressing, thus making a sorted namelist of the OS an essential item to have on hand when debugging the kernel; but nonetheless you can't argue with a darn good idea. Breakpointing the kernel is fun, anyway! -- From the badly beaten keyboards of him who speaks +-best address in textured Technicolor *TyPe* f-O-n-T-s... | | Karl Kleinpaste @ Bell Labs, Columbus 614/860-5107 +---> cbrma!kk @ Ohio State University 614/422-0915 osu-eddie!karl