Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcnc!rti!xyzzy!meissner
From: meissner@xyzzy.UUCP (Michael Meissner)
Newsgroups: comp.unix.wizards
Subject: Re: Debugging the kernel: proper methods?
Message-ID: <121@xyzzy.UUCP>
Date: Mon, 29-Jun-87 23:23:54 EDT
Article-I.D.: xyzzy.121
Posted: Mon Jun 29 23:23:54 1987
Date-Received: Sat, 4-Jul-87 18:41:14 EDT
References: <2713@uw-june.UUCP> <479@winchester.UUCP> <1168@copper.TEK.COM>
Reply-To: meissner@xyzzy.UUCP (Michael Meissner)
Organization: Data General (Languages @ Research Triangle Park, NC.)
Lines: 13

In article <1168@copper.TEK.COM> stevesu@copper.TEK.COM (Steve Summit) writes:
> Nobody has mentioned this yet, so I'll toss it in, although I
> don't know the full details: someone once built adb into the
> kernel, so it could "debug itself," so to speak.  You typed some
> magic command, and the console terminal started talking adb.
> You could set breakpoints and everything.

When I came to Data General 8 years ago, this was ancient history (binding
a real debugger into the kernel).  I have pity for those who try to
debug an OS with print statements.  Our UNIX group now has a source level
debugger available (the source level debugger runs on a host computer and
talks to the assembler level debugger linked in the kernel over async lines).
-- 
Michael Meissner, Data General.		Uucp: ...!mcnc!rti!xyzzy!meissner